feat: Credentials management page

[rbreeze]

List View:

Create:

Edit:

Delete:

With the addition of tabs, I've slightly redesigned and refactored the freightline view as well (the banner text is now outside of the grey area):

[netlify]

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

Name	Link
🔨 Latest commit	69c31e8
🔍 Latest deploy log	https://app.netlify.com/sites/docs-kargo-akuity-io/deploys/66075670f501f20008b6fe45
😎 Deploy Preview	https://deploy-preview-1710.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 44.13%. Comparing base (a24b7d0) to head (69c31e8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1710   +/-   ##
=======================================
  Coverage   44.13%   44.13%           
=======================================
  Files         207      207           
  Lines       13105    13105           
=======================================
  Hits         5784     5784           
  Misses       7078     7078           
  Partials      243      243           

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

[jessesuen]

Approval based on screenshots

[krancour]

@rbreeze repoURL and repoURLPattern are supposed to be mutually exclusive. Is it at all possible that we could just make this one field with a checkbox for "is regular expression" or something?

[rbreeze]

@krancour Oh, there is a front end validation check to make sure that they are mutually exclusive. But I can see how the UI is confusing -- I'll work on an improvement to that part

[hiddeco]

repoURL and repoURLPattern are supposed to be mutually exclusive. Is it at all possible that we could just make this one field with a checkbox for "is regular expression" or something?

This makes me wonder if we can't do more on the back-end to allow both an "exact" match and regular expression in just the repoURL field. Either by allowing e.g. regexp:<regex> like we have been doing in #1270, or by automagically detecting special regex characters.

[krancour]

This makes me wonder if we can't do more on the back-end to allow both an "exact" match and regular expression in just the repoURL field. Either by allowing e.g. regexp: like we have been doing in #1270, or by automagically detecting special regex characters.

After #1270 set that precedent, I can get down with that. I'll work on that now so it gets into v0.5.0... I don't want to break the credential format twice.

@rbreeze those two fields can be combined now, I guess, but I think a checkbox for "is regex" would still be a nicer UX than requiring people to somehow know they can optionally prefix the URL with "regex:".

[rbreeze]

Updated UI to reflect discussed changes: