-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
UI: Env variable to hide yaml submission #11391
Comments
You can use the Workflow Restrictions feature to only allow users to submit via existing templates. Removing the UI button would not necessarily suffice, as the API can still be accessed (e.g. someone could make a request from within their browser console). API permissions are based off k8s RBAC, which is not specific enough to only allow certain kinds of Workflows (other than a If not using Workflow Restrictions, another way to workaround that would be to use policies / admission controllers to create more granular logic. |
would workflow restrictions prevent an adhoc run of a cronworkflow that doesn't use a template? |
I believe it should apply to I've never tried submitting a But if Workflow Restrictions didn't apply to |
Ah right, I forgot, a |
Would be great to hide this button
https://github.com/argoproj/argo-workflows/blob/v3.4.8/ui/src/app/workflows/components/workflow-creator.tsx#L79-L84
Then can allow SSO users to just submit workflows from existing templates but not submit arbitrary new code!
The text was updated successfully, but these errors were encountered: