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

better error handling when trying to destroy a disconnected environment. #63

Open
Elmo33 opened this issue Jul 8, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Elmo33
Copy link
Collaborator

Elmo33 commented Jul 8, 2024

if environment is disconnected for any specific reason and the user runs 'terraform destroy' no resources are actually removed/destroyed, but the env is moved to 'pending deletion' state.

Since no resources are able to be removed due to disconnection, then it would make sense to add some kind of warning for the user that the env is disconnected and there is no point to run terraform destroy and eventually environment shouldnt be moved to 'pending deletion' state either.

@Elmo33
Copy link
Collaborator Author

Elmo33 commented Jul 10, 2024

I faced this issue when I ran the terraform destroy, while reconciler hadnt finished and the env was not connected. But it could happen for any other reason.

@ianaya89 ianaya89 added the enhancement New feature or request label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants