Default secret name is invalid
See original GitHub issueGitHub wont allow a Secret named GITHUB_TOKEN
, it complains Failed to add secret. Name is invalid
.
Then the action complains:
/Users/runner/work/_actions/EndBug/add-and-commit/v4/lib/entrypoint.sh: line 11: GITHUB_TOKEN: unbound variable
Pushing commits to repo...
fatal: could not read Username for 'https://github.com': Device not configured
Pushing tags to repo...
fatal: could not read Username for 'https://github.com': Device not configured
And it wont commit nor push. Would be nice to change the default Secret name.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error: secret $secret_name is invalid · Issue #492 - GitHub
I have deployed kubernetes-external-secrets with IRSA. ... kind: ExternalSecret metadata: name: sample-docker-config-json namespace: default ...
Read more >Secrets | Kubernetes
The name of a Secret object must be a valid DNS subdomain name. You can specify the data and/or the stringData field when...
Read more >Unable to create secret in kubernetes: "Secret is invalid
I found my issue. I was trying to create the Secret object using. Yaml.LoadAllFromString(). which was double encoding my .dockerconfigjson value.
Read more >Auto devops deploy fails due to invalid secret name
For this project we're using gitlab.com and wanted to give the default auto-devops a go, i.e no .gitlab-ci.yml and latest auto devops templates....
Read more >Resolve Secrets Manager secret access errors after ... - AWS
Follow these steps to re-encrypt the secret with the new AWS KMS key using the AWS Management Console or the AWS CLI. AWS...
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
Oh, ok, it works, that comment on the readme about the line should not be modified confused me.
You still are not passing any
GITHUB_TOKEN
env variable to the action. The README has everything you need to know about it. Also, as I said in the previous comment, you can pass any other custom token, as long as there is a validGITHUB_TOKEN
env variable for the action to use.