Atmos Pro Logo

Atmos Pro

ProductPricingDocsBlogChangelog
Create Workspace
← Back to Changelog
Enhancement

Resource Counts, Right in Your Pull Request

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

|September 17, 2026

Older

Your Infrastructure, in Slack

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

Erik is the founder of Cloud Posse and creator of Atmos. With over a decade of experience helping teams adopt Terraform at scale, he is passionate about open-source infrastructure tooling and developer experience.

Book a Meeting
Atmos Pro Logo

Atmos Pro

The fastest way to deploy your apps on AWS with Terraform and GitHub Actions.

GitHubTwitterLinkedInYouTubeSlack

For Developers

  • Quick Start
  • Example Workflows
  • Atmos Documentation
  • Register for Office Hours
  • Join the Slack Community

Enterprise

  • Trust Center
  • Procurement
  • Pricing
  • Contact Sales

Company

  • Support
  • About Cloud Posse
  • Security
  • Blog
  • Media Kit
  • Try our Newsletter

Legal

  • SaaS Agreement
  • Terms of Use
  • Privacy Policy
  • Disclaimer
  • Cookie Policy

© 2026 Cloud Posse, LLC. All rights reserved.

Checking status...
“Has changes” tells you a plan found a difference. Now your pull request comment shows how much will change: +created | ~updated | −destroyed, right beside each component and stack. Completed applies show the resource counts from the apply.
atmos-pro
atmos-probotcommented 1 minute ago
Tip
Atmos Pro Terraform Plancompleted

All dispatched workflows for the affected stacks have completed successfully.

prod/us-east-1vpceks-clusterrds-primarys3-assets
ComponentStackStatus
vpcprod/us-east-13 created, 2 updated, 0 destroyed3 created, 2 updated, 0 destroyed
eks-clusterprod/us-east-1no changesno changes
rds-primaryprod/us-east-11 created, 0 updated, 1 destroyed1 created, 0 updated, 1 destroyed
s3-assetsprod/us-east-1no changesno changes
Total4 created, 2 updated, 1 destroyed4 created, 2 updated, 1 destroyed
Plan complete: 4 of 4 workflows completed. Total: 4 created, 2 updated, 1 destroyed.
View in Atmos Pro →
The Total row adds up the contributing components. A replacement counts as both a creation and a destruction, so it stays visible on both sides of the change. When some rows don’t have counts yet, the total is marked partial.
The badges use a single neutral background with colored numbers and switch automatically between GitHub’s light and dark themes. No-change and error badges use the same neutral surface, with muted or red text to distinguish their status. Older Atmos versions that don’t provide resource counts keep their existing status badges too; unavailable counts are never shown as zero.
You can also review the numeric add, change, and destroy summary alongside the plan in Approvals before approving a deployment. The AI summary adds context without repeating workflow counts as a competing “Totals” footer.