resource/aws_eip_association: fix eventual consistency issue when associating EIP #16808
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.
Community Note
Relates #11617
Relates #12449
Terraform Version
Affected Resource(s)
aws_eip_association
Terraform Configuration
Expected Behavior
aws_eip_association
is created successfully in TF state and in EC2.Actual Behavior
Rarely, the EIP is associated, but in TF state the resource is not recorded due to eventual consistency issue when reading back the association
Output from acceptance testing: