Actions
Bug #7497
closedWe don't need two lifecycle environment options for content view version promote
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.
Updated by Eric Helms almost 10 years ago
- Translation missing: en.field_release set to 14
- Difficulty set to easy
- Triaged changed from No to Yes
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 14 to 23
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 23 to 31
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release deleted (
31)
Updated by Eric Helms over 8 years ago
- Translation missing: en.field_release set to 86
Actions