atmos list stacks fails if backend is not configured
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 176
- Avg merge
- 2d 25m
- Merged PRs (30d)
- 143
Description
Describe the Bug
I cannot use atmos list stacks since it expects all stack backends to be provisioned.
If I use a different S3 backend per stack, I need to provision all of them before I can see the stacks.
Is this expected behavior?
Expected Behavior
atmos list stacks works if the backends do not exist yet in AWS.
Steps to Reproduce
Run atmos list stacks when the S3 bucket for the backend does not exist in AWS yet.
Screenshots
Environment
Linux Ubuntu 24.04, latest terraform and atmos versions to date.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run atmos list stacks with an S3 backend bucket that does not yet exist, then trace how the CLI handles stack backends. Done means the command lists stacks without requiring every configured AWS backend to be provisioned first, while existing backend behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, terraform
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100