fix: destroying an existing instance trigger a bare system reinstall #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
loic-roux-404
changed the title
loic-roux-404
commented
Jul 15, 2024
loic-roux-404
changed the title
loic-roux-404
changed the title
loic-roux-404
commented
Jul 18, 2024
loic-roux-404
force-pushed
the
main
branch
2 times, most recently
from
a9f6d42 to
81e3f16
Compare
loic-roux-404
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When i try to destroy the resource along with a existing instance id i got an 422 unprocessable error.
It is related to a non cancelable instance because it's not managed by terraform but from the subscription started on the dashboard.
I made the choice to move to a default ubuntu in a default reinstall request reseting every instance settings to a consistant default.
Side effect of : #19