Enhancement request - readable name for credentials

[iddoavn]

When creating credentials, it will be useful to have a human-readable explanation of what it each credential set is used for.

[arielshaqed]

I fully support this. I believe you can resolve all issues with the current situation. But the price is hugely increased management and ops burden on our users.

This is one way of resolving it. It is part of many similar user experiences.

Cons

• Not part of the AWS access key ID experience.
• Workaround available: use another user.

Pros

• Part of every token experience. For instance, GitHub tokens force me to attach a name to every token. One of mine is named "Emacs Forge", so I know precisely what it does :-)* Make access key IDs manageable by humans. For example: I leave my laptop somewhere. Which access key ID do I need to delete?

• Automated systems need to attach metadata to a credentials pair. Consider a script that creates a dev env on a lakeFS. It might need to create credentials to put on a Spark profile. Without metadata, that dumps an impossible key management problem onto users.

  We actually had this very problem during the new lakeFS wizard. We dropped that wizard for other (good) reasons, but this was a thorn during use and even during development.

• Workaround (create new accounts) adds considerable administrator management burden.

[github-actions[bot]]

This issue is now marked as stale after 90 days of inactivity, and will be closed soon. To keep it, mark it with the "no stale" label.