Azure Managed HSM - Resource re-creation upon modification of the network configuration

[lucarighes]

Is there an existing issue for this?

• I have searched the existing issues

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 "me too" comments, 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 and review the contribution guide to help.

Description

Currently, Azure Managed HSM resource is being re-created upon modification of the public network access parameter (public_network_access_enabled).

However, this is not the standard behaviour of the resource in the Azure environment. Normally, public network access of Azure Managed HSM resources can be modified without triggering the re-creation of the resource. The re-creation requires a new activation of the Azure Managed HSM (manual upload of public keys and download of the security domain).

Removing this condition on the public_network_access_enabled will allow to have a resource behaviour aligned with the native environment.

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

azurerm_key_vault_managed_hardware_security_module

Potential Terraform Configuration

No response

References

No response

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