Design page for interacting with user-scoped secrets

[evgeniy-scherbina]

Note

The scope of this work is subject to change. Probably not significantly, but there are still a few unknowns as far as what we should expose through the UI

Context

We need to add a new page to the UI for adding user-scoped secrets. This UI page should have full parity with the main API methods for secrets, and should surface all relevant information to the user.

Requirements

• The page should support implementations of the main API methods for working with user-scoped secrets
  • List all secrets that the user has access to
  • Let the user update individual secrets
  • Let the user delete a secret
  • Let the user add a new secret
• The page must be added to the list of options in the User Account section of the UI

Additional thoughts

• Probably have a lot of leeway for how to display each secret. Doesn’t necessarily need to be as a table
• Fields and data that would probably be relevant for each secret:
  • The name of the secret
  • An description for the secret (this field is not required, so in some cases, the content may not be shown)
  • A little badge to indicate that a secret is NOT encrypted
  • Environment variable name (will be all-caps)
  • An indicator for whether the secret is written to a file (which might include the name of the file itself)
  • Time last updated
  • (Possibly) Some indicator for whether the secret is actively being used