Support the --no-wait flag for cf continue-deployment [v8]
#3122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit bf7933c.
chinigo
force-pushed
the
continue-deployment-with-no-wait-v8
branch
from
0696e26 to
7b2b290
Compare
|
@weresch and @joaopapereira I believe I've now incorporated all of your feedback. Please let me know if I've missed anything! Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
Supports the
--no-waitflag for thecf continue-deploymentcommand.Why Is This PR Valuable?
It brings the
continue-deploymentcommand into alignment with other commands that deal with deployments (e.g.cf push,cf restage).How Urgent Is The Change?
Urgent, as we'd like to include this in our pending release.
Related PRs
cf continue-deployment[main] #3123