Repository navigation
fix: disable YAML function processing in list instances - #2170
Conversation
…iring tofu/terraform in PATH
Dependency Review✅ No vulnerabilities or license issues found.Scanned FilesNone |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe changes disable YAML functions in stack description processing by modifying the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2170 +/- ##
=======================================
Coverage 77.17% 77.18%
=======================================
Files 953 953
Lines 90403 90403
=======================================
+ Hits 69771 69780 +9
+ Misses 16556 16552 -4
+ Partials 4076 4071 -5
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
…se/atmos into goruha/native-ci-terraform-plan * 'goruha/native-ci-terraform-plan' of github.com:cloudposse/atmos: fix: disable YAML function processing in list instances to avoid requiring tofu/terraform in PATH (#2170)
|
These changes were released in v1.210.0-test.12. |
What
Disable YAML function processing (
processYamlFunctions) inatmos list instanceswhile keeping template processing enabled.Why
atmos list instancescallsExecuteDescribeStackswithprocessYamlFunctions: true, which triggers execution of YAML functions like!terraform.outputandatmos.Component(). These shell out totofu/terraform, causing failures when those binaries aren't in$PATH— even though listing instances doesn't need to resolve function values.Template processing is kept enabled because templates can create additional stacks and components that should be included as instances.
Ref
atmos list instancesfails withexec: "tofu": executable file not found in $PATHSummary by CodeRabbit
Changes
Tests