Restructure credential naming for scalability

Task 9182 · Done · Coder · created · updated

See creds here as Operator: <https://app.jaah.ai/credentials> Their names and structure is all over the place with some old stuff like Skynet, gmind for system cred that has nothing to do with gmind, etc. Users creds at the root, etc Propose an elegant way to restructure the naming that would support thousands of users, companies and clearly identify core/operator system creds from tenant system, tenant project, etc. Do web research for best practices

Outcome

Credentials now have one structural home (system/org/project/personal) shown as a locked prefix; lowercase names unique per home; runner paths org/ projects/<p>/ me/; no by-name lookups; operators edit any org's credentials via act-as. 4 PRs merged, dev deployed; 39 prod + 46 dev rows renamed in the UI. Prod personal/connection renames and project homes wait for the next master promotion (listed in report). Drafts 9194, 9214. Memory: none applied; proposed 0.

Pull request Pull request Pull request Pull request

Artifacts

Activity

  • Created
  • Run
  • Runner started
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Runner ended (done)