mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1098] Enhancement: Overwrite workflow env vars with passed in env vars #629
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#629
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 @liamphmurphy on GitHub (Apr 2, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1098
Describe feature
Say we have a workflow that at either the job or steps layer has the following variable declaration:
At the time of writing, passing in an environment variable such as
act -j job --env foo=another-valuewill not overwritefoo, and the value will bebarwhen the workflow runs inact.The use case here is that I can overwrite the default behavior of the workflow in some way; such as where the workflow should find config files, for example. This could allow for testing without having to change the actual workflow first.
I came across this when I wanted to change the path to output some TLS certs that my app uses from what my workflow usually does.
Let me know if I missed something and it does actually work; I'm happy to go ahead and make the PR as well.
@liamphmurphy commented on GitHub (Apr 4, 2022):
Closing since #1100 was merged in
needsjob output #1528