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

Updating docs #169

Merged
merged 3 commits into from
Mar 17, 2016
Merged

Updating docs #169

merged 3 commits into from
Mar 17, 2016

Conversation

lostintangent
Copy link
Member

Updates the CLI docs to include a new TOC, as well as include details for the new rollout parameter, patch command, and expanded promote command. I also took it upon myself to organize the three release variants a little bit.


2. If you rollback a deployment whose latest release is an "active" rollout, the rollout value will be cleared, effectively "deactivating" the rollout behavior

3. Unlike the `mandatory` and `description` fields, when you promote a release from one deployment to another, it will not propogate the `rollout` property, and therefore, if you want to new release, in the target deployment, to have a rollout value, you need to explicitly set it when you call the `promote` command.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

propagate the rollout property... if you want do a new release

@shishirx34
Copy link
Contributor

Looks good.

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.

3 participants