Attempt to fix #23601

[danielcweber]

When a cluster is restored from a snapshot, resourceClusterUpdate is called, passing the engine-version along to ModifyDBCluster. This will always fail, even when the engine-version has not changed. The solution might be to omit the version from the arguments in case the resource has been freshly created.

Community Note

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

Relates #23601

[tgourley01]

We tested this locally and it resolves the restore from snapshot issue. Can we get some attention on this to get it merged?

[ran2806]

We are blocked by this issue. So I took the change from this branch and built the provider locally. I have tested following flows.

1. Restoring cluster from snapshot.
2. Destroying restored cluster.
3. Creating blank cluster.
4. Updating blank cluster.
5. Destroying blank cluster.

All the above scenarios are working good.

[ewbankkit]

@danielcweber Thanks for the contribution 🎉 👏.
I have rolled the functionality into #28051.

[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.