This release is a pre-release and may not be stable for production use.
Description
This is the pyramid webapp for the Twonicorn web api/ui. It’s rich, lives in a castle, and can do magic.
Changelog
Wishlist
feature: Defined user role(s) that can promote to prod within a defined day/time window.
feature: Support for listing/promoting all staged promotions by application.
feature: Auto creation of JIRA tickets.
cleanup: Fix all the pylint warnings.
2.8.4
- feature: Local users functionality for those who don’t want to use
Active Directory/LDAP for authentication.
2.8.3
bugfix: Forgot to rename parameter of api.
2.8.2
feature: Adding support for local users/groups
feature: Support for jars as an artifact type.
feature: Support for tars as an artifact type.
bugfix: Renaming ambiguous ‘users’ columns to ‘updated_by.
2.8.1
bugfix: Chaging the artifact type for a deploy not updating db.
- bugfix: Unable to get artifact type from db if there is not
an existing artifact assignment.
2.8
- feature: Moving group management to the db. Additions to the control
panel to manage them.
2.7
- feature: Control panel for admins, allows to create and edit applications
and deploys within the UI.
2.6
feature: New PUT API. Injection no longer requires direct DB access.
2.5.1
feature: Adding python package support
2.5
bugfix: API no longer requires auth for deployments.
2.4
bugfix: hardcode cgm version of mysql-connector-python.
2.3
feature: Implimentation of the API endpoint.
2.2
bugfix: Fix exception when a deploy has no entry in the database yet.
2.1
bugfix: explicitly inserting with utc timestamp.
2.0
Switched to SQLAlchemy
1.5.1
Fixing a bad cut and paste in the qat repeat of deploys.pt
1.5
Moving dependency to TwonicornLib from TwonicornWebLib.
1.4
bugfix: fixed bug where promote links were shown for confs.
1.3
removing the cheeky commentary on some of the pages.
1.2
bugfix: fixed a bug when the referer.url was an outside site (jenkins).
1.1
Support for performing promotions via the UI. Replaces the functionality of the promote jenkins job.
1.0
Initial release
1 maintainer
Metadata
1 maintainer
Release files for TwonicornWeb 2.8.5dev20150320091112
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| TwonicornWeb-2.8.5dev20150320091112.tar.gz | 265.5 kB | Without provenance | Details for TwonicornWeb-2.8.5dev20150320091112.tar.gz |
Release files / TwonicornWeb-2.8.5dev20150320091112.tar.gz
| Download URL | TwonicornWeb-2.8.5dev20150320091112.tar.gz |
|---|---|
| Size | 265.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b66194b1313a0e8eb506ef778ce4c858ce423386bb2ddffc30cdb6fc845ae34
|
|
BLAKE2b-256 checksum How to use checksums |
e1674fe1a1576e485264cb50f6b7a2c49350eac2105af890c37290a61e76858f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TwonicornWeb 2.8.5dev20150320091112
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
