UI: Inactivate buttons for actions not allowed by current permissions

[Radolumbo]

Summary

Recently made a change to the argo-server role permissions to prevent our users from creating things via the UI. Based this on the recommendation here: https://argoproj.github.io/argo-workflows/security/#read-only

It would be REALLY nice if the Argo UI was aware of the fact that the current user does not have permission to, say, "+SUBMIT NEW WORKFLOW" and greyed out that button. Instead, it is still clickable, and just fails when the user tries to create a workflow.

Use Cases

Any time you want to use the UI as a read-only option (or any iteration of permissions on the server, maybe you only want to block users from deleting workflow, then that button should grey out).

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

[Radolumbo]

Honestly, I might even argue this is a bug...

[simster7]

Great point, I'll work on this

[Radolumbo]

@simster7 Any update on this? Might look to pick this up on my team sometime soon if not.

[simster7]

Sorry, haven;t had a chance to work on this. Feel free to pick it up @Radolumbo