Skip to content

Conversation

ironcladlou
Copy link
Contributor

Note that you can still supply a deployment name (for backwards compatibility), but I don't see a good reason to promote that in the latest docs.

@ironcladlou
Copy link
Contributor Author

cc @adellape

@adellape
Copy link
Contributor

@ironcladlou I take it this is as of openshift/origin#3643 in Origin, and wouldn't make it into OSE until 3.0.1 at the earliest?

Also, to verify for --to-version, are the "version" numbers equivalent to the Deployment #1, Deployment #2, etc reported when describing a dc? So for example if Deployment #3 was currently active, to roll back to Deployment #2 you'd use --to-version=2?

@ironcladlou
Copy link
Contributor Author

@adellape

@ironcladlou I take it this is as of openshift/origin#3643 in Origin, and wouldn't make it into OSE until 3.0.1 at the earliest?

Oops, yeah. I should have linked that in.

Also, to verify for --to-version, are the "version" numbers equivalent to the Deployment #1, Deployment #2, etc reported when describing a dc? So for example if Deployment #3 was currently active, to roll back to Deployment #2 you'd use --to-version=2?

That's correct.

adellape added a commit that referenced this pull request Jul 13, 2015
@adellape adellape merged commit 205acc6 into openshift:master Jul 13, 2015
@ironcladlou ironcladlou deleted the rollback-improvements branch July 29, 2015 17:14
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