atmos vendor update

Check each Git-backed source in your vendor.yaml for a newer version — honoring any per-source constraints — and update the version field in place, preserving comments, anchors, and Go templates such as {{.Version}} in source URLs.

atmos vendor update --help

Usage

atmos vendor update [--check] [--pull] [--component <name>] [--tags <a,b>] [--outdated]

Sources whose version is templated ({{...}}) or whose source is not a Git repository are skipped and reported. Updates are written to the file that declares each source, including imported manifests.

Examples

# Dry run: show what would be updated.
atmos vendor update --check

# Update all Git-backed sources.
atmos vendor update

# Update versions and then pull the new components.
atmos vendor update --pull

# Update a single component, or by tags.
atmos vendor update --component vpc
atmos vendor update --tags networking,aws

# Show only sources with an available update.
atmos vendor update --check --outdated

Version constraints

Per-source constraints control which upstream versions are eligible:

sources:
  - component: "vpc"
    source: "github.com/cloudposse/terraform-aws-components"
    version: "1.323.0"
    constraints:
      version: "^1.0.0"            # semver constraint (Masterminds/semver)
      excluded_versions:
        - "1.2.3"                  # a specific bad version
        - "1.5.*"                  # an entire broken series
      no_prereleases: true         # skip alpha/beta/rc

Flags

--check

Dry run: show available updates without modifying any files.

--pull

After updating versions, run atmos vendor pull.

--component / -c (string)

Update only this component.

--tags (string)

Update only components carrying any of these comma-separated tags.

--outdated

Show only sources with an available update.

--file (string, default ./vendor.yaml)

The vendor manifest to start from (imports are followed).

note

Version detection is supported for Git sources only (tags via git ls-remote), which covers GitHub, GitLab, Bitbucket, and self-hosted Git. OCI, S3, GCS, and HTTP sources are skipped. Private repositories are not yet supported.