Bug #10623
closedNeed way to promote latest version of Content View to next environment via hammer
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1219585
Currently you must use the version ID of a Content View to promote to the next environment:
hammer content-view version promote --organization Engineering --content-view-id 5 --to-lifecycle-environment DEV --id 59
This makes automation hard if you wish to 'auto promote' after a publish as you are forced to query version IDs to fill out the --id param above.
Ideally we would not require the specification of the version and it would just take the latest and you could promote via:
hammer content-view version promote --organization Engineering --content-view-id 5 --to-lifecycle-environment DEV
if we required specification of the prior you could do:
hammer content-view version promote --organization Engineering --content-view-id 5 --to-lifecycle-environment DEV --from-lifecycle-environment Library
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/hammer-cli-katello/pull/296 added
- Pull request deleted (
)
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release set to 31
- Triaged changed from No to Yes
Updated by dustin tsang over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset hammer-cli-katello|35cbd6fd566b7d13faaa7eb2dd0158a13128f10b.
Updated by Bryan Kearney almost 9 years ago
- Category changed from Web UI to Content Views