Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to delete an env only locally if no more exists? #14025

Closed
realtebo opened this issue Nov 25, 2024 · 3 comments
Closed

How to delete an env only locally if no more exists? #14025

realtebo opened this issue Nov 25, 2024 · 3 comments
Labels
multienv Issues tied to multiple environment feature in the CLI pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question

Comments

@realtebo
Copy link

realtebo commented Nov 25, 2024

Amplify CLI Version

11.0.0

Question

I have a lot of envs locally.
But a lot of them don't exist anymore

How to delete?

% amplify env list

| Environments |
| ------------ |
| *prod        |
| newprod      |
| newestprod   |
| provaprod    |
| staging      |
% amplify env remove provaprov
🛑 Environment name is invalid.

Please note: In my amplify/team-provider-info.json i only have prod and staging

@realtebo realtebo added pending-triage Issue is pending triage question General question labels Nov 25, 2024
@ykethan
Copy link
Member

ykethan commented Nov 26, 2024

Hey @realtebo, thank you for reaching out. If the environment was removed on the Amplify console and team-provider-info.json, it appear the reference does still exist in the amplify/.config/local-aws-info.json file. you should be able to remove the provaprov block from the file and run amplify env list which should no longer show the env.

do note if you do not see the amplify/.config folder, you will need to enable this in the .vscode/settings.json by setting "amplify/.config": false,

@ykethan ykethan added pending-response Issue is pending response from the issue author multienv Issues tied to multiple environment feature in the CLI labels Nov 26, 2024
@ykethan
Copy link
Member

ykethan commented Dec 13, 2024

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
multienv Issues tied to multiple environment feature in the CLI pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question
Projects
None yet
Development

No branches or pull requests

2 participants