Atmos Pro premium features and integrations
View All Tags
Fetching private Terraform modules, Atmos source: components, and vendored artifacts in CI has
always meant handing a long-lived, over-privileged GitHub credential to your pipeline — a PAT, a
machine user, or a deploy key, sitting in a CI secret. Atmos Pro STS replaces that with
just-in-time, least-privilege, short-lived GitHub tokens that are minted at the start of a run and
revoked at the end — with zero .tf changes.
atmos describe affected --upload now works under GITHUB_EVENT_NAME=merge_group, so Atmos Pro can correctly conclude check runs on the synthetic commits GitHub creates when a PR enters a merge queue. To control what runs on those synthetic commits, declare a new settings.pro.merge_group.checks_requested.workflows block in your stack config and point it at the workflow you want the queue to dispatch (in most cases, the same plan workflow you already use for pull_request.synchronize).
Atmos now supports server-side commits via the Atmos Pro GitHub App. The new atmos pro commit command
sends your changes to Atmos Pro, which creates the commit using its GitHub App installation — ensuring
commits trigger CI workflows.
Atmos now automatically chunks large payloads when uploading affected stacks and instances to Atmos Pro, eliminating HTTP 413 errors for large infrastructure repositories.
For teams using Atmos Pro, the Atmos CLI now pushes instance status directly to the Atmos Pro dashboard the moment a plan or apply completes. The dashboard reflects the real state of every component within seconds — no polling, no waiting for webhooks, no stale data.
Updated the Atmos Pro integration to use query parameters for the instances API endpoint, fixing issues with stack and component names containing slashes and improving API compatibility.
