Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluating local relative paths #318

Open
austinwilburnedo opened this issue Feb 29, 2024 · 0 comments
Open

Evaluating local relative paths #318

austinwilburnedo opened this issue Feb 29, 2024 · 0 comments

Comments

@austinwilburnedo
Copy link

austinwilburnedo commented Feb 29, 2024

ERRO[0002] Error: Error in function call

ERRO[0002]   on /home/atlantis/.atlantis/repos/org/repo/81/default/sonarqube/staging/us-west-2/parameter-store/terragrunt.hcl line 10, in locals:
ERRO[0002]   10:   secretsyaml = yamldecode(sops_decrypt_file("encrypted_secrets.yaml"))
ERRO[0002]
ERRO[0002] Call to function "sops_decrypt_file" failed: Failed to read "encrypted_secrets.yaml": open encrypted_secrets.yaml: no such file or directory.

The file does exist there (in the child path: /home/atlantis/.atlantis/repos/org/repo/81/default/sonarqube/staging/us-west-2/parameter-store/encrypted_secrets.yaml.

In other terragrunt.hcl's where we have defined the path with: ${get_terragrunt_dir()}/encrypted_secrets.yaml it is able to look at the correct path, but anytime we do relative it does not.

How can we get the tool to respect relative path for locals ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants