Some secrets are marked as "Unknown access context"
See original GitHub issueJob with a secret as an env var:
process-managers:
needs: start-time
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
...
is shown as
But: https://docs.github.com/en/actions/reference/encrypted-secrets#using-encrypted-secrets-in-a-workflow And it also works just fine.
Via https://github.com/prisma/e2e-tests/blob/dev/.github/workflows/test.yaml
Issue Analytics
- State:
- Created 2 years ago
- Reactions:19
- Comments:17 (3 by maintainers)
Top Results From Across the Web
Resolve Secrets Manager secret access errors after ... - AWS
How can I resolve issues accessing an encrypted AWS Secrets Manager ... "Access to KMS is not allowed", "InternalFailure", or "An unknown ......
Read more >Secret Detection - GitLab Docs
Anyone with access to the repository could use the secrets for malicious purposes. Exposed secrets must be considered compromised and be replaced, which...
Read more >java.io.IOException: Invalid Keystore format - Stack Overflow
I tried many things, but none of them worked. And when I click more details I get this: at sun.security.provider.JavaKeyStore.engineLoad(Unknown Source) atsun.
Read more >The SPYSCAPE Glossary of Spy Terms
Agent. As an agent, you work secretly for an intelligence service, offering secrets or operational support. While the FBI calls certain officers 'agents', ......
Read more >Guide for the Standard Form (SF) 86
1.2 Why am I required to have a background investigation? ... 1.3 Is completing the form mandatory in order to get a position...
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
FWIW the weird commonality here is that the error only seems to happen with secrets that begin with
S
. Very strange indeed.I get this for secrets used inside
run:
clauses.This is fine:
This isn’t: