Open tmccombs opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @tmccombs 👋 Thank you for taking the time to raise this, and for providing a solid description of the issue (as always)! I'm seeing this while triaging issues, but wanted to take the time to acknowledge the sentiment around the previous report on this. I can absolutely see where you're coming from, and (as the project's community manager) am thinking about that experience a lot right now. Hopefully I'll have some more news for you around that before too long. One thing I do want to note is that linking to the previous issue like you did is immensely helpful, and is something that we take into consideration when working on prioritizing efforts, so thank you very much for doing so.
As an aside, you've been contributing to the provider for quite a while now, so I'm not sure how long it's been since you've needed to review our contribution guide. With that in mind, I wanted to make sure you were aware of a relatively new section we've added regarding Slack, in case you'd be interested 🙂.
Hello, Is there been any investigation/fix on this issue? this seems like a very big issue in the provider.
Hello Team !!
I am still facing the same issue whether any fix for this ?
Terraform Core Version
1.6.2
AWS Provider Version
5.21.0
Affected Resource(s)
Expected Behavior
If a table has replicas, then I should be able to remove the replicas and disable the stream in the same action.
Actual Behavior
If you try to disable streaming in the same apply that you remove all replicas, you get an Error saying that you can't disable streaming for a global table.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Usage of the module:
Steps to Reproduce
Create a table that has one or more replicas, with streaming enabled. Then try to delete the replicas and disable streaming.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
This was previously reported as https://github.com/hashicorp/terraform-provider-aws/issues/19342, but that was closed due to inactivity.
p.s. it is super annoying to search for a bug I encounter only to find that it has been reported, but closed due to inactivity.
Would you like to implement a fix?
None