Project

General

Profile

Actions

Bug #7497

closed

We don't need two lifecycle environment options for content view version promote

Added by David Davis over 9 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Hammer
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

In the CLI, we require a 'to' environment and a 'from' environment which is inconsistent with the API. The API just takes an environment id. Moreover, it doesn't look like the 'from-lifecycle-environment' option is actually doing anything other than verifying that the env exists:

❯ hammer content-view version promote --id 6 --to-lifecycle-environment Dev --from-lifecycle-environment Staging --organization-id 1                                            
[............................................................................................................................................................................................] [100%]
Task f056786c-d150-48f7-be63-571e0e384a07: success

Note that my env path is Library -> Dev -> Staging.

https://github.com/Katello/hammer-cli-katello/pull/214

Actions #1

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 14
  • Difficulty set to easy
  • Triaged changed from No to Yes
Actions #2

Updated by Eric Helms about 9 years ago

  • translation missing: en.field_release changed from 14 to 23
Actions #3

Updated by Eric Helms about 9 years ago

  • translation missing: en.field_release changed from 23 to 31
Actions #4

Updated by Eric Helms about 9 years ago

  • translation missing: en.field_release deleted (31)
Actions #5

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 86
Actions #6

Updated by Eric Helms about 8 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF