Support the update of KxCluster databases and code configuration

[matthiasweaser]

Description

This pull request introduces changes that allow users to update KxCluster databases and code configuration without having to destroy and recreate a KxCluster resource.

Testing

For acceptance tests relating to these changes, environment deletion is triggered immediately after cluster deletion since cluster deletion no longer waits for the deletion workflow to complete before being marked as "deleted". We are working on a fix for this but essentially this bug is on our side and non-terraform related other than breaking all our existing cluster acceptance tests.

This results in our acceptance tests successfully updating the cluster resource but failing at the resource cleanup step. All other steps of the tests completed successfully.

Acceptance Tests updated:

• TestAccFinSpaceKxCluster_commandLineArgs
• TestAccFinSpaceKxCluster_initializationScript
• TestAccFinSpaceKxCluster_code

Manual testing has been done in place to ensure that the behavior of cluster updates are as desired.

References

API documentation for UpdateKxClusterDatabases: https://docs.aws.amazon.com/cli/latest/reference/finspace/update-kx-cluster-databases.html

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

Welcome @matthiasweaser 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃

[jar-b]

Thanks for your contribution, @matthiasweaser! 👏

[github-actions]

This functionality has been released in v5.24.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.