Project

General

Profile

Actions

Bug #10623

closed

Need way to promote latest version of Content View to next environment via hammer

Added by dustin tsang almost 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Content Views
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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

Actions

Also available in: Atom PDF