Title | Application or use case | Runtime | Language or framework | Type of secret | Secret injection workflow | Secrets rotation workflow | Availability requirement |
---|---|---|---|---|---|---|---|
Description | Name or description | Determines authentication method | Determines SDK or Vault agent | Determines which secrets engines | How does the app or use case get the secret? | How does the app or use case handle rotation? | Important information about application availability |
Examples | payments application Jenkins |
Cloud service provider: AWS, Microsoft Azure, Google Cloud, other Runtime: virtual machines, Nomad, Kubernetes, other |
Spring .NET Go Python Other |
Static database username and password Other static credentials Cloud service provider credentials JSON web token API tokens Certificates |
Environment variable Properties file Configuration server |
Restart application Application self-reloads |
Cannot restart: business critical Cannot restart: no high availability architecture Rolling restart: highly available Restart acceptable |
-
-
Save joatmon08/1abc3f05355fbccaf4328beaac85431e to your computer and use it in GitHub Desktop.
Vault developer enablement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment