Skip to content
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

[2pt] Create workflow for sending callback urls and schedule it at the end of adviser #2558

Closed
Tracked by #1741
KPostOffice opened this issue May 11, 2022 · 4 comments · Fixed by #2617
Closed
Tracked by #1741
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@KPostOffice
Copy link
Member

Is your feature request related to a problem? Please describe.
Need to schedule task to send all callback urls

Describe the solution you'd like
Add a workflow to run workflow-helpers task which takes results and sends them to each url defined in a secret and then add a task at the end of adviser which schedules this workflow (see: https://argoproj.github.io/argo-workflows/workflow-submitting-workflow/)

@KPostOffice KPostOffice added the kind/feature Categorizes issue or PR as related to a new feature. label May 11, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label May 11, 2022
@KPostOffice KPostOffice changed the title Create workflow for sending callback urls and schedule it at the end of adviser [2pt] Create workflow for sending callback urls and schedule it at the end of adviser May 23, 2022
@KPostOffice
Copy link
Member Author

/sig user-experience

@sesheta sesheta added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label May 23, 2022
@harshad16
Copy link
Member

/triage accepted
/priority backlog

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Jun 6, 2022
@sesheta
Copy link
Member

sesheta commented Sep 4, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2022
@harshad16
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 6, 2022
@codificat codificat moved this to 📋 Backlog in Planning Board Sep 24, 2022
Repository owner moved this from 📋 Backlog to ✅ Done in Planning Board Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants