-
Notifications
You must be signed in to change notification settings - Fork 26
FLPATH-303: workflow rollback #332
FLPATH-303: workflow rollback #332
Conversation
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
aab6fc2
to
33bf328
Compare
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
33bf328
to
341edb6
Compare
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@RichardW98: This pull request references FLPATH-303 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
341edb6
to
d9d6350
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add rollback example and integration test.
How user can specify whether to run rollback or not?
I will add some instruction in readme. I think whether to run rollback should be managed by workflow admin. Users are usually only interested in how they can make next workflow success, rather than the rollback process of failed workflow. Also same workflows should have the same rules to run rollback or not. so I think we don't need user to specify it from UI |
ee943f8
to
45aff49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
45aff49
to
0300040
Compare
0300040
to
5e12063
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anludke The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
User may want to rollback executions if the workflow is failed
misleading swagger response with list:
Which issue(s) this PR fixes:
Fixes #FLPATH-303 #FLPATH-358
Change type
Impacted services
Checklist