Open AndrewCharlesHay opened 1 week ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @AndrewCharlesHay 👋 Thank you for taking the time to raise this! I noticed that you're using an aliased provider in your example configuration. Can you provide the detail for that (and I suppose the non-aliased provider as well) so that whoever picks this up to look at it has a more complete picture of the configuration? If it's possible to supply debug logging (redacted as needed), that's often helpful as well.
@justinretzolk I added the provider and debug 🐛 info. It looks like the destination_region
argument is not being passed into the SDK which makes sense. According to the API documentation it expects destination_region
in the presigned URL
Terraform Core Version
1.8.3
AWS Provider Version
5.73.0
Affected Resource(s)
aws_db_snapshot_copy
Expected Behavior
When I pass in destination_region I expect the snapshot to be created in that region.
Actual Behavior
It makes the snapshot in the same account as the original snapshot. In this case that is us-east-2.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Create a
aws_db_snapshot_copy
with a region different than the originalDebug Output
I set the log level to debug. The info below was redacted partially. I think the most important log info is the http.request for CopyDBSnapshot below
http.request.body=
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None