mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #610] Issue: Secrets do not appear to get used when used in env #402
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#402
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jmetzmeier on GitHub (Apr 6, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/610
Act version
Expected behaviour
The workflow should use secrets supplied via the
-soption. This workflow functions properly in Github actions.Actual behaviour
When the secret gets to
curl, it contains the valueXXXXX-XXXXX-XXXXX-XXXXXWorkflow 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
-vso 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-XXXXXactoutputLog
@github-actions[bot] commented on GitHub (May 7, 2021):
Issue is stale and will be closed in 14 days unless there is new activity
@ThrowJojo commented on GitHub (May 14, 2021):
I was able to get this to work by passing the
--insecure-secretsflag@jmetzmeier commented on GitHub (May 14, 2021):
I apologize for messing up the triage on this one by accidentally closing the issue.
@github-actions[bot] commented on GitHub (Jun 14, 2021):
Issue is stale and will be closed in 14 days unless there is new activity