Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #17067 - Removing from environment options #462

Closed
wants to merge 1 commit into from

Conversation

daviddavis
Copy link
Contributor

@daviddavis daviddavis commented Oct 24, 2016

Seems like the from_lifecycle_environment option doesn't actually do anything as this command succeeds:

hammer content-view version promote --id 9 --from-lifecycle-environment ENVTHATDOESNOTEXIST --to-lifecycle-environment Dev --organization-id 1

I can even run promote without the option:

hammer content-view version promote --id 9 --to-lifecycle-environment Test --organization-id 1

@akofink
Copy link
Member

akofink commented Oct 24, 2016

I'm not sure this command is broken. What about this command?

hammer content-view version promote --content-view-id 2 --organization-id 1 --to-lifecycle-environment development --from-lifecycle-environment Library

This is working for me on the master branch. I have an environment named 'development', and I'm using the 'Library' environment to find the content view version inside of the specified content view. If I leave off the --from-lifecycle-environment option, I get

Could not promote the content view:
  Error: found more than one content_view_version

The --from-lifecycle-environment option is used to find the content view version, so if you specify the ID, you will, of course, not need it.

@daviddavis
Copy link
Contributor Author

@akofink good catch. Closing.

@daviddavis daviddavis closed this Oct 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants