[Enhancement]: Ability to update SVM active directory configuration

[varunrai]

Description

Currently, once the SVM has been created there is no way to update the configuration to join the Active Directory or if Active Directory configuration change is needed.

Scenario: Create an SVM without joining the domain. Subsequently add the configuration in terraform code to include AD configuration.

Current Behaviour: This triggers a re-creation of the volumes and SVM.
Expected Behaviour: SVM should not be replaced. Instead the relevant API to be called in AWS to update the configuration.

Affected Resource(s) and/or Data Source(s)

aws_fsx_ontap_storage_virtual_machine

Potential Terraform Configuration

No response

References

There was a recent enhancement to the AWS SDK and also Management Console to include the ability for updating the AD configuration.

The AWS SDK was updated to include the SVM AD configuration update.
API_UpdateSvmActiveDirectoryConfiguration

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Related #33199

[github-actions]

This functionality has been released in v5.18.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.