cloudposse/atmos v1.205.1-rc.2

on GitHub

• Removed misleading component dependency examples that showed unsupported syntax
• Clarified that the dependencies section currently supports tool version requirements only
• Added admonition directing users to settings.depends_on for component execution order
• Updated frontmatter, intro, and use cases to reflect tool-only focus
• Added reference link to settings.depends_on documentation

why

The documentation previously conflated two separate concepts: tool dependencies (currently implemented via /dependencies/tools) and component dependencies (only available via settings.depends_on). The examples showing component dependency syntax were misleading since they're not yet supported in the /dependencies section. This change prevents user confusion and guides them to the correct feature.

references

This fixes documentation confusion around component dependencies vs tool dependencies. The plan is to consolidate these features in a future release, so this admonition acknowledges that intent.

Summary by CodeRabbit

• Documentation
  • Clarified dependencies documentation to emphasize tool version requirements as the primary focus
  • Expanded tool dependency configuration guidance, including configuration scopes, version formats, and inheritance behavior
  • Added information directing users to settings for managing component execution order
  • Updated related documentation references to include component dependencies guidance

_{✏️ Tip: You can customize this high-level summary in your review settings.}

• Fixed pattern matching bug where excluded_paths in component.yaml and vendor.yaml weren't matching simple filename patterns like "providers.tf"
• Fixed logic error where combined excluded_paths + included_paths wasn't working correctly
• Added comprehensive unit tests and YAML-based integration tests for the fix

why

• Users could not use simple filename patterns in excluded_paths without the **/ glob prefix
• When both excluded_paths and included_paths were specified, the include filter was never applied
• Patterns were matched against absolute temp paths instead of relative paths, causing simple patterns to always fail

references

• Fixes vendoring with simple filename exclusions like excluded_paths: ["providers.tf"]
• Enables proper filtering when both exclude and include patterns are specified together

Summary by CodeRabbit

• Bug Fixes

  • Improved vendor file exclusion/inclusion logic to apply patterns correctly and consistently.
  • Fixed path matching to work with relative paths, enabling simpler exclusion/inclusion patterns without directory prefixes.
  • Added early exclusion checks for clearer and more efficient filtering behavior.

• Tests

  • Added comprehensive test suite for vendor exclude/include scenarios covering various pattern combinations.