Add --wait, -w flag to run-task #1861
Merged
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
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/170160892 The labels on this github issue will be updated when the story is started. |
|
Bumping this due to a user reaching out, we are planning on merging this PR for the first minor release post V7 GA :)! |
|
What's the state on this PR, is it still being tracked? |
|
I'd like to follow up to see if this PR is still relevant. |
|
I would still like to get that feature. :) |
Dito, would enormously improve the scriptability with the cf cli |
|
Any updates on this? I'd also like to use this in my scripts. |
|
Our team is understaffed. It could take a while to get to this via the backlog. |
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Addresses Issue cloudfoundry#1104 Authored-by: Zach Robinson <zrobinson@pivotal.io>
|
|
@a-b I've updated the PR to remove conflicts and to target v7 branch. hope that helps when you get a chance to review. |
|
Thank you @zrob ! |
|
@zrob is employed by VMware, so we are going to proceed with this merge. |
stephanme
added a commit
to stephanme/cli
that referenced
this pull request
Dec 8, 2022
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (cloudfoundry#1861) to v8 Addresses Issue cloudfoundry#1104, cloudfoundry#2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <stephan.merker@sap.com>
a-b
pushed a commit
to stephanme/cli
that referenced
this pull request
Dec 13, 2022
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (cloudfoundry#1861) to v8 Addresses Issue cloudfoundry#1104, cloudfoundry#2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <stephan.merker@sap.com>
stephanme
added a commit
to stephanme/cli
that referenced
this pull request
Dec 14, 2022
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (cloudfoundry#1861) to v8 Addresses Issue cloudfoundry#1104, cloudfoundry#2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <stephan.merker@sap.com>
jdgonzaleza
pushed a commit
to stephanme/cli
that referenced
this pull request
Dec 15, 2022
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (cloudfoundry#1861) to v8 Addresses Issue cloudfoundry#1104, cloudfoundry#2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <stephan.merker@sap.com>
a-b
pushed a commit
to stephanme/cli
that referenced
this pull request
Jun 8, 2023
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (cloudfoundry#1861) to v8 Addresses Issue cloudfoundry#1104, cloudfoundry#2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <stephan.merker@sap.com>
stephanme
added a commit
to stephanme/cli
that referenced
this pull request
Oct 12, 2023
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (cloudfoundry#1861) to v8 Addresses Issue cloudfoundry#1104, cloudfoundry#2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <stephan.merker@sap.com>
ccjaimes
pushed a commit
that referenced
this pull request
Oct 12, 2023
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (#1861) to v8 Addresses Issue #1104, #2238 Authored-by: Zach Robinson <zrobinson@pivotal.io>
ccjaimes
pushed a commit
that referenced
this pull request
Oct 12, 2023
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (#1861) to v8 Addresses Issue #1104, #2238 Authored-by: Zach Robinson <zrobinson@pivotal.io>
ccjaimes
added a commit
that referenced
this pull request
Oct 13, 2023
When the wait flag is supplied to run-task, the cli will not exit until the task enters a terminal state; SUCCEEDED or FAILED. The cli exits 0 when the task succeeds and exits 1 when the task fails. This improves the scriptability of tasks. They can be run serially in a script. Cherry-pick of 8671a5b (#1861) to v8 Addresses Issue #1104, #2238 Authored-by: Zach Robinson <zrobinson@pivotal.io> Co-authored-by: Stephan Merker <merker.stephan@gmail.com>
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.
When the wait flag is supplied to run-task, the cli will
not exit until the task enters a terminal state; SUCCEEDED or FAILED.
The cli exits 0 when the task succeeds and exits 1 when the task fails.
This improves the scriptability of tasks. They can be run
serially in a script.
Addresses Issue #1104
This affects v7 only.
Does not address the --log request in the associated issue.