Support for azurerm_backup_protected_vm features backup_vault recover_soft_deleted_backup

[mpjtaylor]

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 when a machine goes into soft delete in a backup vault terraform cannot configure it.

already exists - to be managed via Terraform this resource needs to be imported into the State

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

azurerm_backup_protected_vm

Potential Terraform Configuration

provider "azurerm" {
  features {
    backup_vault {
      recover_soft_deleted_backup  = true
    }
  }
  skip_provider_registration = true
}

resource "azurerm_backup_protected_vm" "protected_intent_azurerm" {
  resource_group_name = data.azurerm_recovery_services_vault.vault[0].resource_group_name
  recovery_vault_name = data.azurerm_recovery_services_vault.vault[0].name
  source_vm_id        = local.virtual_machine_id
  backup_policy_id    = local.support_backup_policy_id
}

References

No response

[mpjtaylor]

can you confirm the documentation is correct indication is it defaults to false but doesn't seem to be the case?
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/features-block

The recovery_services_vault block supports the following:

recover_soft_deleted_backup_protected_vm - (Optional) Should the azurerm_backup_protected_vm resource recover a Soft-Deleted protected VM? Defaults to false.

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