feat(ui): Permissions Management

[rbreeze]

Fixes #1920

[netlify]

✅ Deploy Preview for docs-kargo-akuity-io ready!

Name	Link
🔨 Latest commit	9cce92f
🔍 Latest deploy log	https://app.netlify.com/sites/docs-kargo-akuity-io/deploys/66356bc2c81c010008248f81
😎 Deploy Preview	https://deploy-preview-1939.kargo.akuity.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.25%. Comparing base (2a26e2a) to head (9cce92f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1939   +/-   ##
=======================================
  Coverage   46.25%   46.25%           
=======================================
  Files         235      235           
  Lines       16004    16004           
=======================================
  Hits         7402     7402           
  Misses       8242     8242           
  Partials      360      360           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jessesuen]

I didn't think about how an RBAC UI might might look like until now, but now that I've seen it. I have suggestions on ways to simplify the UX.

Here are things I'd like to simplify:

1. This UI supports arbitrary K8s resources with text fields for apiVersion/group/kind. I'm proposing to limit this to Kargo-specific GVKs so that users don't have to type groups, apiVersions, resources, etc... Also, there's no reason we need to support other things like deployments/pods/etc... In other words, when adding a rule, they would only be able to select from: Stages, Promotions, Warehouses, Secrets, AnalysisTemplates, and we would format this with the proper GVK in the rule before submitting to API.

2. Similar to 1, verbs are well known: create, update, delete, patch, list, promote (promote only applies to stages). Instead of a text field, a checkbox of predefined verbs would be helpful.

3. The emails/sub/groups can be under a subtitle called "OIDC bindings". Instead of subs, let's call it Subjects.

4. Though a form is nice, I still think a YAML editor would be desired.

Let me know if any of this is feasible in short timeframe of v0.6. Otherwise, I'm willing for this to be done as a follow-up in v0.7

[rbreeze]

Updated interface:

[krancour]

🔥