I think there's an issue with <github-action-atmos...
# github-actions
m
I think there's an issue with github-action-atmos-affected-stacks - if we start using atmos lookups, then the action fails, because there's no terraform in the action 😄 issues/41
✅ 2
e
Aha, looks like the action needs to install terraform. Good catch
@Igor Rodionov ☝️
Cc @Gabriela Campana (Cloud Posse) @Andriy Knysh (Cloud Posse)
m
It actually was installing terraform before, but was removed on v3 release 😄
r
Maybe that was so you can choose between installing terraform and tofu ?
https://github.com/cloudposse/github-action-atmos-affected-stacks/releases/tag/3.0.0
The notable changes in v3 are:
v3 works only with atmos >= 1.63.0
v3 drops install-terraform input because terraform is not required for affected stacks call
v3 drops atmos-gitops-config-path input and the ./.github/config/atmos-gitops.yaml config file. Now you have to use GitHub Actions environment variables to specify the location of the atmos.yaml.
e
> v3 drops install-terraform input because terraform is not required for affected stacks call
This was true, until we added
atmos.Component
function, which I believe executes
terraform outputs
@Andriy Knysh (Cloud Posse) , can you confirm? cc @Igor Rodionov
a
if you are using atmos.Component in templates, then yes, terraform must be installed
e
@Gabriela Campana (Cloud Posse) let's create a task to restore this functionality, with a feature flag.
✅ 1
For now, @Marat Bakeev you should be able to work around this by adding the step to install terraform (or open tofu) in your GHA workflow
m
Unfortunately, it will still fail, even with terraform installed. It also wants node. For now, we just hardcoded our values and are not using lookups, but it would be great to be able to use them.
a
what wants Node? it’s probably in some of your templates
m
I'm using reference arch from you guys, I don't know. I enabled templates to get the lookups working, and it started asking for node
a
it’s probably related to the GH actions. Nothing in the templates needs Node (unless it’s some function in the templates)
e
@Matt Calhoun @Dan Miller (Cloud Posse) any ideas? This is based on our latest refarch from last week
@Marat Bakeev by any chance is the terraform component using node under the hood? e.g. with a local exec?
m
@Erik Osterman (Cloud Posse) honestly, I'm not sure. We didn't add anything!
Here is the PR to rollback terraform installation. Waiting for a review to merge
@Marat Bakeev The PR was released at v3.1.0
Could you pls rerun your workflows to see if the problem solved
m
@Alexander Matveev see this?
a
@Marat Bakeev Got it. Thanks!
m
@Igor Rodionov it seems to have fixed it, thanks!
👍 2