-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
Issue: Secrets do not appear to get used when used in env #610
Labels
area/workflow
Relating to workflow definitions
kind/bug
Something isn't working
needs-work
Extra attention is needed
stale-exempt
Exempt from stale
Milestone
Comments
Issue is stale and will be closed in 14 days unless there is new activity |
catthehacker
added
area/workflow
Relating to workflow definitions
and removed
stale
labels
May 11, 2021
I was able to get this to work by passing the |
I apologize for messing up the triage on this one by accidentally closing the issue. |
Issue is stale and will be closed in 14 days unless there is new activity |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/workflow
Relating to workflow definitions
kind/bug
Something isn't working
needs-work
Extra attention is needed
stale-exempt
Exempt from stale
Act version
Expected behaviour
The workflow should use secrets supplied via the
-s
option. This workflow functions properly in Github actions.Actual behaviour
When the secret gets to
curl
, it contains the valueXXXXX-XXXXX-XXXXX-XXXXX
Workflow and/or repository
workflow
Steps to reproduce
Use a workflow file that exports the value of a secret to an environment variable. In my curl example, I am using
-v
so I can see the headers sent in the request. I am running withact --insecure-secrets -s WISER_PACKAGES=REDACTED
| > GET /download/REDACTED/0.0.4/9f531f2642f938ad0f9beea59c9edcf811af85c773fb897bc6a523f3b4380bba HTTP/2
| > Host: npm.pkg.github.com
| > authorization: Basic eC1hY2Nlc3MtdG9rZW46WFhYWFgtWFhYWFgtWFhYWFgtWFhYWFg=
| > user-agent: curl/7.68.0
| > accept: /
This authorization string decodes to
x-access-token:XXXXX-XXXXX-XXXXX-XXXXX
act
outputLog
The text was updated successfully, but these errors were encountered: