aws-amplify / aws-amplify/amplify-cli
rerunning pull on a modifiable yes project prompts for profile selection three times
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
_No response_
### If applicable, what version of Node.js are you using?
_No response_
### Amplify CLI Version
12.4.0
### What operating system are you using?
mac
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
### Describe the bug
On studio disabled project, running amplify pull --appId and selecting yes and rerunning the command prompts for profile three times
https://github.com/aws-amplify/amplify-cli/assets/87995712/a08f816c-9eb6-4568-966c-8704e1e28d3d
doesnt occur on a project that didnt have studio enabled before.
### Expected behavior
prompt for profile one time.
### Reproduction steps
1. create a new application on AWS console
2. disable studio
3. create empty folder locally
4. run `amplify pull --appId ` with the app-id filled in. select `yes` for allow modifying backend
5. rerun command and observe it prompts for profile three times
### Project Identifier
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
### Before submitting, please confirm:
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
Contributor guide
Research direction
Reproduce the issue with the listed `amplify pull --appId ` steps on a project where Studio was disabled, then compare the first run with the rerun and trace the profile prompts. Done means the rerun prompts for the profile only once, while preserving the expected behavior for a project that never had Studio enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100