Replies: 1 comment
-
I received a response on the argo-workflows slack, stating that the resume api endpoint is namespace bound. So with the right combination of k8s service accounts, SSO, and leveraging a specific namespace, we should be able to achieve this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'd like to leverage manual approval functionality for a database migrations flow, where members can approve a database migration to move forward. However, I'd like to lock it down so that only specific, certain sets of users and/or user-groups can actually approve, not just anyone that can log in to argo workflows.
I found some related discussions but they don't specify if this functionality can be used with targeted user permissions:
Beta Was this translation helpful? Give feedback.
All reactions