-
Notifications
You must be signed in to change notification settings - Fork 170
[WaitApproval] Notify events of Approved/WaitApproval in Piped side #5632
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
Conversation
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Signed-off-by: t-kikuc <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5632 +/- ##
==========================================
+ Coverage 26.58% 26.62% +0.04%
==========================================
Files 477 478 +1
Lines 50657 50818 +161
==========================================
+ Hits 13465 13531 +66
- Misses 36134 36221 +87
- Partials 1058 1066 +8 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
if err != nil { | ||
s.logger.Error("failed to get the list of users", zap.Error(err)) | ||
} | ||
approver, _ := s.metadataStore.StageGet(stage.Id, "pipecd.dev.Approver") // TODO: Make the key to be a const. |
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.
[help wanted]
How about not notifying if 'approver' is empty?
For the situation like the stage ended due to reasons other than approvals.
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This PR was closed because it has been stalled for 7 days with no activity. Feel free to reopen if still applicable. |
What this PR does:
Instead of triggering the events exactly at start/end of the approval, trigger them at start/end of the stage.
WaitApproval
Event: Trigger at the same timing asStageStarted
Approved
Event: Trigger at the same timing asStageSucceeded
approver
field will be passed from a plugin indirectly via metadataStoreWhy we need it:
Instead of #5613, this PR does not add RPCs for simplicity of the interface.
Which issue(s) this PR fixes:
Part of #5367
Does this PR introduce a user-facing change?: