You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
[This is a documenting issue.]
Immediately after a role is created, AWS sometimes returns a unique ID (e.g., AROAQ7SSZBKHRKPWRZUN6) in the ARN field. This can create problems with drift detection and problems like seen in #8905. The problem appears to be random and may depend on how busy AWS is currently.
The AWS provider should not ever include a unique ID in aws_iam_role.arn regardless what AWS returns.
Affected Resource(s)
aws_iam_role
Expected Behavior
ARN attribute should always be an actual ARN (e.g., arn:aws:iam::12345678901:role/tf-acc-test-7531775986226331375-mercedes).
Actual Behavior
Occassionally (rarely), aws_iam_role.arn is a unique ID (e.g., AROAQ7SSZBKHRKPWRZUN6).
Steps to Reproduce
terraform apply
Wait for planets to align
Preferably try this when AWS is really busy (maybe during re:invent?)
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
[This is a documenting issue.]
Immediately after a role is created, AWS sometimes returns a unique ID (e.g., AROAQ7SSZBKHRKPWRZUN6) in the ARN field. This can create problems with drift detection and problems like seen in #8905. The problem appears to be random and may depend on how busy AWS is currently.
The AWS provider should not ever include a unique ID in
aws_iam_role.arn
regardless what AWS returns.Affected Resource(s)
Expected Behavior
ARN attribute should always be an actual ARN (e.g.,
arn:aws:iam::12345678901:role/tf-acc-test-7531775986226331375-mercedes
).Actual Behavior
Occassionally (rarely),
aws_iam_role.arn
is a unique ID (e.g.,AROAQ7SSZBKHRKPWRZUN6
).Steps to Reproduce
terraform apply
References
The text was updated successfully, but these errors were encountered: