Query the resource version prior to making an update #46
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
Storing the resource version in Terraform state doesn't quite do what we'd expect. If we tell Terraform that it is computed, we aren't able to read it during `apply` and thus can't pass it as part of the request. If we tall Terraform that it is not computed, it is assumed to be constant, and Terraform will bark at us when we attempt to mutate it. To remedy this, we read the namespace just before updating or deleting it to get a recent resource version and use that in the request. If a concurrent request causes the update or delete to fail, the user will need to run `terraform apply` again.
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.
Storing the resource version in Terraform state doesn't quite do what we'd expect. If we tell Terraform that it is computed, we aren't able to read it during
applyand thus can't pass it as part of the request. If we tall Terraform that it is not computed, it is assumed to be constant, and Terraform will bark at us when we attempt to mutate it.To remedy this, we read the namespace just before updating or deleting it to get a recent resource version and use that in the request. If a concurrent request causes the update or delete to fail, the user will need to run
terraform applyagain.