azurerm_databricks_root_dbfs_customer_managed_key - missing support for keys from a Managed HSM Key Vault

[MaguellSandifort]

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 comments along the lines of "+1", "me too" or "any updates", 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.

Terraform Version

1.6.1

AzureRM Provider Version

3.116.0

Affected Resource(s)/Data Source(s)

azurerm_databricks_root_dbfs_customer_managed_key

Terraform Configuration Files

resource "azurerm_databricks_workspace_root_dbfs_customer_managed_key" "example" {
  workspace_id     = azurerm_databricks_workspace.example.id
  key_vault_key_id = "https://<hsm_id>.managedhsm.azure.net/keys/<key_name>/<key_version>"
}

Debug Output/Panic Output

Error: parsing "https://XXX.managedhsm.azure.net/keys/KEY_NAME/KEY_VERSION": internal-error: Managed HSM IDs are not supported as Key Vault Nested Items

Expected Behaviour

The parameter key_vault_key_id should accept a value with .managedhsm.. Alternatively a new field should be added specifically for managed HSM KVs (e.g. managed_hsm_key_vault_key_id).

Actual Behaviour

The error in Debug Output is thrown

In the azurerm_databricks_root_dbfs_customer_managed_key resource, the key vault id is passed to a keyvaultParser
→ the parser explicitly checks for .managedhsm. in the id . If it exists, the error experienced is thrown.

Steps to Reproduce

Run a terraform plan

Important Factoids

No response

References

#21470
#22977
#26392
#26357
#26338
#27436
#27738