Bump github.com/cloudposse/atmos from 1.88.0 to 1.90.0

[dependabot]

Bumps github.com/cloudposse/atmos from 1.88.0 to 1.90.0.

Release notes

Sourced from github.com/cloudposse/atmos's releases.

v1.90.0

This change improves the templating within vendor manifests slightly: It officially adds support for the Component field to both source and targets.

These features were already supported but mostly undocumented and hidden behind an implicit switch: The templating was only triggered if the Version field was set. Which was also the only officially supported field.

In reality though all fields from the current source definition were available but in the state they were currently in, depending on the order of the templates.

With this change

• It is clearly documented which fields are supported in which YAML values.
• Only the two static fields are supported.
• The values are always templated.

Theoretically this could be a breaking change if somebody used no version field but curly braces in their paths. Or relied on the half-populated source data structure to refer to unsupported fields. If xkcd 1172 applies it should be possible to amend this logic to add more officially supported fields.

why

I was looking for a way to restructure our vendoring like the examples in examples/demo-vendoring/vendor.yaml to avoid copy and paste errors when we release new component versions.

I actually only found out about that demo when I was done writing this code since the templating was never triggered without a version field and the documentation didn't mention it.

references

• https://github.com/cloudposse/atmos/blob/v1.88.1/examples/demo-vendoring/vendor.yaml
• https://atmos.tools/core-concepts/vendor/vendor-manifest/#vendoring-manifest

Summary by CodeRabbit

• New Features

  • Enhanced vendoring configuration with support for dynamic component referencing in vendor.yaml.
  • Improved handling of source and targets attributes for better organization and flexibility.

• Documentation

  • Updated documentation for vendoring configuration, including clearer instructions and examples for managing multiple vendor manifests.
  • Added explanations for included_paths and excluded_paths attributes to improve understanding.

... (truncated)

Commits

• 94e0226 Always template vendor source and targets (#712)
• fecba15 Fix a reference to an undefined output in GitHub Actions (#718)
• 6439a64 Install Terraform to fix CI failure that Terraform is not found (#717)
• 8c6591b Improve error stack trace. Add --stack flag to atmos describe affected co...
• 7c41087 Correct outdated 'myapp' references in simple tutorial (#707)
• 373219a Fix incorrect terraform flag in simple tutorial workflow example (#709)
• 878c26f Fix typos (#703)
• 3971989 Fix version command in simple tutorial (#705)
• 64319be docs: add installation guides for asdf and Mise (#699)
• fe90ea3 Use Latest Atmos GitHub Workflows Examples with RemoteFile Component (#695)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)