You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The secrets configured in tfaction.yaml are not being set as environment variables by export-secrets.
However, when the same secrets configuration is set in tfaction-root.yaml, it works properly.
The environment variable NEW_RELIC_API_KEY is not being set.
Important Factoids
This issue seems similar to #1564, where despite the log message in export-secrets stating The list of secret names passed to the action: NEWRELIC_API_KEY_DEV, the environment variable is not being set.
tfaction version
v1.4.0
Overview
The secrets configured in tfaction.yaml are not being set as environment variables by export-secrets.
However, when the same secrets configuration is set in tfaction-root.yaml, it works properly.
How to reproduce
tfaction-root.yaml
tfaction.yaml
GitHub Actions Workflow
I have created a workflow based on this example as a reference.
I am using
secrets: inherit
to pass secrets to the reusable workflow.GitHub Actions' log
Expected behaviour
The log states:
export the secret NEWRELIC_API_KEY_DEV as the environment variable NEW_RELIC_API_KEY
.Below is the configuration of secrets written in tfaction-root.yaml:
tfaction-root.yaml
tfaction.yaml
Actual behaviour
The environment variable NEW_RELIC_API_KEY is not being set.
Important Factoids
This issue seems similar to #1564, where despite the log message in export-secrets stating
The list of secret names passed to the action: NEWRELIC_API_KEY_DEV
, the environment variable is not being set.After reviewing the code in the following files:
I couldn't find the part where it retrieves secrets from tfaction.yaml."
Note
No response
The text was updated successfully, but these errors were encountered: