Bump github.com/cloudposse/atmos from 1.70.0 to 1.77.0

[dependabot]

Bumps github.com/cloudposse/atmos from 1.70.0 to 1.77.0.

Release notes

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

v1.77.0

what

• Update atmos validate stacks command
• Improve stack validation error messages

why

• When checking for misconfiguration and duplication of components in stacks, throw errors only if the duplicate component configurations in the same stack are different (this will allow importing the base default/abstract components into many stack manifest files)

• The atmos validate stacks command check the following

  • All YAML manifest files for YAML errors and inconsistencies

  • All imports: if they are configured correctly, have valid data types, and point to existing manifest files

  • Schema: if all sections in all YAML manifest files are correctly configured and have valid data types

  • Misconfiguration and duplication of components in stacks. If the same Atmos component in the same Atmos stack is defined in more than one stack manifest file, and the component configurations are different, an error message will be displayed similar to the following:

    The Atmos component 'vpc' in the stack 'plat-ue2-dev' is defined in more than one
    top-level stack manifest file: orgs/acme/plat/dev/us-east-2-extras, orgs/acme/plat/dev/us-east-2.
    The component configurations in the stack manifests are different.
    To check and compare the component configurations in the stack manifests, run the following commands:
    
    atmos describe component vpc -s orgs/acme/plat/dev/us-east-2-extras
    atmos describe component vpc -s orgs/acme/plat/dev/us-east-2
    
    You can use the '--file' flag to write the results of the above commands to files
    (refer to https://atmos.tools/cli/commands/describe/component).
    You can then use the Linux 'diff' command to compare the files line by line and show the differences
    (refer to https://man7.org/linux/man-pages/man1/diff.1.html)
    When searching for the component 'vpc' in the stack 'plat-ue2-dev', Atmos can't decide which
    stack manifest file to use to get configuration for the component. This is a stack misconfiguration.
    Consider the following solutions to fix the issue:
    
    
    Ensure that the same instance of the Atmos 'vpc' component in the stack 'plat-ue2-dev'
    is only defined once (in one YAML stack manifest file)
    
    
    When defining multiple instances of the same component in the stack,
    ensure each has a unique name
    
    

... (truncated)

Commits

• 6f7a5dd Update atmos validate stacks command (#611)
• 3e0983a Add Atmos manifest lists merge strategies (#609)
• d00aa78 Improve atmos validate stacks and atmos describe affected commands (#608)
• 85d7c15 Use Darker Theme, Add File Component (#607)
• df1c9bb Update Atmos logs. Update docs (#605)
• f7aa382 Allow Go templates in metadata.component section. Add `components.terrafo...
• 774d30d chore: Updated Tips for Creating GitHub App for Component Updater (#593)
• 054ca5b Update gomplate datasources. Add env and evaluations sections to Go ...
• 2b85f6f Update atmos describe affected command. Update docs (#590)
• 7eb0a88 updated setup requirements for GitHub Apps (#589)
• 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)

[dependabot]

Superseded by #399.