allow_major_version_upgrade for Neptune

[mrtngrbmn]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue 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 issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

I tried to update a Neptune cluster from 1.0.2.2 to 1.1.1.0 but got the message
Error: Failed to modify Neptune Cluster (...): InvalidParameterCombination: The AllowMajorVersionUpgrade flag must be present when upgrading to a new major version.
status code: 400, request id: c965c5fe-ccca-4a42-91f3-e238a022bf5e

There is no allow_major_version_upgrade for aws_neptune_cluster available (like in aws_db_instance)

After that it was possible to upgrade using the AWS console

New or Affected Resource(s)

aws_neptune_cluster

using terraform 0.15.5 and aws v3.75.1, but also the latest version documentation for 4.12.1 does not show such an argument.

[deividferreira-hotmart]

I also tried to upgrade a Neptune cluster from 1.0.5.1 to 1.1.0.0 and got the same message.

[github-actions]

This functionality has been released in v4.17.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 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.