Unable to add secrets that start with "@"
See original GitHub issueAs a result of https://github.com/fugue/credstash/issues/19 it seems that it is now impossible to add secrets that begin with @
:
$ credstash put -v 1 'jenkins_ad_bind_pass' '@4=saCD0nF'
usage: credstash put [-h] [-k KEY] [-v VERSION] [-a]
[-d {SHA,MD5,RIPEMD,SHA384,SHA224,SHA256,SHA512,WHIRLPOOL}]
credential value [context [context ...]]
credstash put: error: argument value: Unable to read file 4=saCD0nF
The root cause is that the “@” is interpreted by credstash as denoting a file name argument. As a result, there seems to be no way to add an actual secret if it begins with an “@” character.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Resolve Secrets Manager secret access errors after ... - AWS
1. Open the Secrets Manager console. · 2. In Secret name, choose your secret. · 3. Choose Actions, and then choose dropdown list,...
Read more >Github: Failed to add secret. Please try again - Stack Overflow
I just created a IAM User in AWS and am now wanting to add the access key ID and the secret access key...
Read more >Add an AWS Secrets Manager - Harness.io Docs
Before You Begin · Permissions: Test AWS Permissions · Step 1: Configure Secrets Manager · Step 2: Display Name · Option: Credentials Type....
Read more >Unable to create secrets in secretsmanager #1262 - GitHub
Stood up localstack with just the secretsmanager service running and im unable to create/get/list secrets errors with same error stating ...
Read more >Set and retrieve a secret from Key Vault using Azure portal
To access Azure Key Vault, you'll need an Azure subscription. If you don't already have a subscription, create a free account before you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It should be noted that the workaround above adds a newline as part of the secret. It should be:
How would the workaround work with contexts? I tried to echo -n… with contexts in it, doesnt work