Incorrect documentation for data_protection_backup_instance_disk

[jrstreng]

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

Terraform (and AzureRM Provider) Version

Terraform 1.0.04
Azurerm 2.72.0

Affected Resource(s)

azurerm_data_protection_backup_instance_disk

Terraform Configuration Files

#example code from documentation.
resource "azurerm_data_protection_backup_instance_disk" "example" {
  name                         = "example-backup-instance"
  resource_group_name          = azurerm_resource_group.rg.name
  vault_id                     = azurerm_data_protection_backup_vault.example.id
  disk_id                      = azurerm_managed_disk.example.id
  snapshot_resource_group_name = azurerm_resource_group.rg.name
  backup_policy_id             = azurerm_data_protection_backup_policy_disk.example.id
}

Documentation states location and resource_group_name are required.
Resource_group_name returns error in validate with arguments is not expected here.
Location is just missing from example.

Debug Output

Panic Output

Expected Behaviour

Validate should be successful.

Actual Behaviour

An argument named "resource_group_name" is not expected here.
Removing resource_group_name makes validate/apply go successful.

Steps to Reproduce

1. terraform validate

Important Factoids

References

• #0000

[github-actions]

This functionality has been released in v2.76.0 of the Terraform 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.