-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow updates to aws_msk_connector connector_configuration #41685
Allow updates to aws_msk_connector connector_configuration #41685
Conversation
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
|
The fork is owned by an organization, I cannot enable |
The lint failed due to something I didn't change (afaict), but it did bring to my attention that |
@epbensimpson Thanks for the contribution 🎉 👏. |
6dd9cfa
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
1 similar comment
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
Description
In January 2025 MSK was updated to allow changes to a connector's configuration without recreating the connector.
The
aws_mskconnect_connector
needs updating to handle this.UpdateConnector
only accepts one ofcapacity
orconnectorConfiguration
per call. As such, we need to check which of these has changes and call the API separately for each change. We also need to get the new connector version in between the requests.Relations
Closes #40914
References
Output from Acceptance Testing
The test should pass (verified the expected values in the console), but ran into some errors on the cleanup due to restricted delete permissions for kafka clusters and S3 buckets on my end.