We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending the Vault secret engine would help many in the kapitan-community (feedback channel + kapitan working group).
I want to share how I/we in my company tend to use the vault k+v store and its features.
{version}/{product-group}/{environment}-{provider-or-host}/{in-use-by}/{secret-type}/{name}
v1/some-product/production-cluster-eu14/jenkins/aws-credentials/rootnonotreally
v1/some-other-product/production-saucelabs/jenkins/saucelabs-credentials/web-team
v1/some-thing/staging-cluster-us87/our-service/slack-token/chat-token
{ "options": { "cas": 0 }, "data": { "creator": "firstname.lastname", "created-at": "2021-07-10-07:06", "expires-at": "2023-07-10-07:06", "encryption": "plain", "material": "02af2bb18847318ae5c738d29c9e18ef1a3afae12ca25e323a186c07b8aff0c1" } }
curl \ --header "X-Vault-Token: ..." \ --request POST \ --data @payload.json \ https://${VAULT_URL}/v1/v1/some-product/production-cluster-eu14/jenkins/aws-credentials/rootnonotreally
Alternatively with vault CLI
export VAULT_ROOT_TOKEN=<myToken> export VAULT_TOKEN=<myToken> export VAULT_ADDR=${VAULT_URL} vault kv put ops_kv/v1/some-product/production-cluster-eu14/jenkins/aws-credentials/rootnonotreally material=02af2bb18847318ae5c738d29c9e18ef1a3afae12ca25e323a186c07b8aff0c1 creator=firstname.lastname encryption=plain created-at=$(date "+%Y-%m-%d-%H:%M") expires-at=2023-07-10-07:06
parameters: better_secret: value: ?{vaultkv:targets/${target_name}/aws-credentials/rootnonotreally||randomstr|base64}
We can make use of the /sys/tools/random endpoint
/sys/tools/random
parameters: better_secret: value: ?{vaultkv:targets/${target_name}/aws-credentials/rootnonotreally||vaultrandom:32|base64} value: ?{vaultkv:targets/${target_name}/aws-credentials/chat-token||vaultrandom:32|hex}
We may can use something out of these links:
The text was updated successfully, but these errors were encountered:
Fixed with #1053
Sorry, something went wrong.
MatteoVoges
Successfully merging a pull request may close this issue.
Feature
Extending the Vault secret engine would help many in the kapitan-community (feedback channel + kapitan working group).
I want to share how I/we in my company tend to use the vault k+v store and its features.
Our Concept
Templated
{version}/{product-group}/{environment}-{provider-or-host}/{in-use-by}/{secret-type}/{name}
Example
v1/some-product/production-cluster-eu14/jenkins/aws-credentials/rootnonotreally
v1/some-other-product/production-saucelabs/jenkins/saucelabs-credentials/web-team
v1/some-thing/staging-cluster-us87/our-service/slack-token/chat-token
Execution
Payload
API-Call
Vault-CLI
Alternatively with vault CLI
Kapitan
Built In generators
Vault Secret generators (similar to GKMS?)
We can make use of the
/sys/tools/random
endpointDocs
We may can use something out of these links:
The text was updated successfully, but these errors were encountered: