Closed ricbartm closed 2 years ago
:tada: This issue has been resolved in version 1.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Thanks for fixing this issue upstream. I planned to send a PR but got my week cannibalised, and you have been faster than me. 🎉 ❤️
thanks to @henworth 🎉
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.
Describe the bug This is a race condition. We have seen the DMS Subnet Group creation failing because the IAM Role does not exist yet in the account.
Looks like the
aws_dms_replication_subnet_group.this
resource needs a dependency onaws_iam_role.dms_access_for_endpoint
To Reproduce It's a race condition. Provisioning a DMS task from scratch several times will cause the bug to show up.
Expected behavior Provisioning of DMS resources apply in the first attempt.
Additional context