mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1601] Multiline secret workaround logging sensitive information #803
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#803
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 @mryhmln on GitHub (Feb 2, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1601
Bug report info
Command used with act
Describe issue
I just tried the workaround for using a multiline secret as described in issue #123. Act did manage to pull in the secret value, but then inside my GitHub Actions Workflow where I am calling a Bash script to pass in the value, it's logging the unobfuscated version of the value instead of "***", as it typically does with secret values.
I included a relevant portion of the output log file. Also note that my .dev.twilio_crt.secrets file contains my multiline secret value and both .dev.secrets and .dev env contain standard single-line environment/secret values.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
Here's the contents of my envsubst Bash script:
@github-actions[bot] commented on GitHub (Aug 2, 2023):
Issue is stale and will be closed in 14 days unless there is new activity