fix: Allow specifying ARN as sns_topic_name if region/account is different for aws_cloudtrail #41279
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
This PR is to fix an issue introduced by #41168 where
sns_topic_name
is always read as the name instead of ARN, even for an SNS topic in another region or account, for theaws_cloudtrail
resource.The documentation is NOT specify that one can specify an SNS topic ARN as
sns_topic_name
, nor does it specify that the the SNS topic can be in a different region (and presumably different account). I will open an AWS support case separately to seek clarification, but for now we need to fix the regression.If you think think we should simply roll back the change and fix it again for 6.x for better compatibility, let me know.
Relations
Closes #41262
References
n/a - documentation is wrong anyway...
Output from Acceptance Testing
Note: I am not sure why
TestAccCloudTrail_serial/Trail/migrateV0
always fail in my environment.