You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, a number of us have created secrets (API keys, passwords, tokens) in an ad hoc fashion, and each devops has their own keyring (gpg, 1Password, etc.), and worse these sets are disjoint. That means if any one of us perhaps got hit by a bus, access to those secrets would die off too.
We need a way to share and pool our secrets while also keeping them safe from prying eyes and doling them out on a need-to-know basis.
π Additional Details
No response
Acceptance Criteria
Given When I perform Then I expect
βοΈ Engineering Details
No response
The text was updated successfully, but these errors were encountered:
Checked for duplicates
No - I haven't checked
π§βπ¬ User Persona(s)
PDS Engineering Node devops
πͺ Motivation
Right now, a number of us have created secrets (API keys, passwords, tokens) in an ad hoc fashion, and each devops has their own keyring (gpg, 1Password, etc.), and worse these sets are disjoint. That means if any one of us perhaps got hit by a bus, access to those secrets would die off too.
We need a way to share and pool our secrets while also keeping them safe from prying eyes and doling them out on a need-to-know basis.
π Additional Details
No response
Acceptance Criteria
Given
When I perform
Then I expect
βοΈ Engineering Details
No response
The text was updated successfully, but these errors were encountered: