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
When using different GitHub actions (e.g., atmos plan, atmos apply, etc.) that rely on the cloudposse/github-action-atmos-get-setting and reference another component with !terraform.output, the process fails. This happens because, instead of receiving the expected JSON output from the terraform output, it receives a message generated here: terraform_outputs.go#L221.
This behavior is triggered during the execution of this command: atmos.ts#L5.
Expected Behavior
When referencing another component with !terraform.output, the GitHub actions should receive a properly formatted JSON object containing the Terraform output values, not an error message.
Steps to Reproduce
Use a GitHub workflow that includes cloudposse/github-action-atmos-get-setting.
Reference another component output using !terraform.output in your atmos stack configuration.
Run the workflow.
Observe that the actions fail due to receiving a message instead of valid JSON.
Environment
OS: Linux (e.g., Ubuntu GitHub Actions runner)
Version: Atmos version v1.155.0
The text was updated successfully, but these errors were encountered:
Describe the Bug
When using different GitHub actions (e.g., atmos plan, atmos apply, etc.) that rely on the
cloudposse/github-action-atmos-get-setting
and reference another component with!terraform.output
, the process fails. This happens because, instead of receiving the expected JSON output from the terraform output, it receives a message generated here:terraform_outputs.go#L221.
This behavior is triggered during the execution of this command:
atmos.ts#L5.
Expected Behavior
When referencing another component with !terraform.output, the GitHub actions should receive a properly formatted JSON object containing the Terraform output values, not an error message.
Steps to Reproduce
cloudposse/github-action-atmos-get-setting
.!terraform.output
in your atmos stack configuration.Environment
The text was updated successfully, but these errors were encountered: