cloudposse / cloudposse/atmos

atmos list stacks prompts for identity

Open
#1,950 5 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
Go
Stars
1.4k
Forks
175
Avg merge
2d 3h
Merged PRs (30d)
134

Description

### Describe the Bug

I am playing around with the `atmos auth` feature right now to see if it can replace our current solution.

One annoying thing popped up right away: As soon as I have it configured but no profile is marked as default (we need to select the proper identity based on the stack, ie. use "Component-Level Configuration") I am asked for a profile each time I run command slike `atmos list stacks` or `atmos list components`.

There may be some odd edge cases where people might need authentication for these meta commands but 99% of the people shouldn't need it so I'd say no login should be required to execute these.

### Expected Behavior

`atmos list ...` and `atmos describe ...` should not prompt for an identity if none is given.

### Steps to Reproduce

1. Configure auth
2. Run ´atmos list stacks`

### Screenshots

_No response_

### Environment

- Version 1.203.0

### Additional Context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing authentication prompting from the `atmos list stacks` reproduction and compare it with the `atmos list components` and `atmos describe ...` command paths. Confirm the behavior with auth configured and no default profile; done means these meta commands no longer prompt for an identity when none is provided.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.