Packer orchestration: init/build/validate/inspect/output, machine image building, template management, source management
Atmos wraps the Packer CLI to provide stack-aware orchestration of machine image builds. Instead of manually managing variable files, template paths, and environment configuration for each Packer component, Atmos resolves the full configuration from stack manifests and handles all of these concerns automatically.
When you run any atmos packer command, Atmos performs the following sequence:
vars defined for the component
in the stack, making them available to the Packer template.source field and the target
directory does not exist, Atmos downloads the component via JIT vendoring before proceeding.--templatesettings.packer.template.*.pkr.hclenv values defined in the stack configuration.packer init, build, validate, inspect, etc. with
the generated variable file and any additional flags.This means a single command like atmos packer build ubuntu-base -s ue2-dev replaces what would normally
require manually writing variable files, configuring paths, and running packer directly.
Packer components are configured under the components.packer section of stack manifests: