Fix aws_ec2_instance_connect_endpoint/fips_dns_name in non-US regions #37939
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.
Description
Outside of FIPS-supported regions (us-east-1, us-east-2, us-west-1, us-west-2, ca-central-1, ca-west-1, us-gov-east-1, us-gov-west-1) AWS API responses for EICE do not contain the
FipsDnsName
property. That leaves the resource in an infinitefips_dns_name = (known after apply)
loop and results in crashes on apply.This makes sure
fips_dns_name
is initialized with an empty string if theFipsDnsName
property is missing from the AWS API response.This does not change the resource's documented behavior or the behavior covered by tests.
Relations
Closes #37920
References
TestAcc Output
For
us-east-1
:For
eu-west-1
: