atmos vendor
Vendoring copies components, stacks, and other dependencies from shared sources into your repository. Use it to reuse existing infrastructure code while choosing which versions to adopt, reviewing changes before an upgrade, and keeping a local copy you can inspect and customize.
Declare the sources and versions in vendor.yaml, then pull them into your project.
Commit the vendored files to track dependency changes alongside your own code. See
Vendoring for the concepts and configuration options.
Learn how to configure vendoring in your atmos.yaml, including token injection and vendor manifest paths.
Usage
Subcommands
atmos vendor get and atmos vendor set address sources by component name.
atmos vendor config reads and edits any field in
vendor.yaml using dot-notation paths.
Remove lock-owned vendored files, refusing to delete files modified since they were vendored.
5 items
Show the Git diff between two versions of a vendored component without a local checkout.
Read the pinned version of a vendored component from vendor.yaml.
Use this command to pull sources and mixins from remote repositories for Terraform and Helmfile components and stacks.
Set the pinned version of a vendored component in vendor.yaml, preserving comments, anchors, and templates.
Update vendored component versions to the latest allowed release, preserving comments, anchors, and templates.
Verify vendored files match vendor.lock.yaml, reporting drift for CI.
