Added controlled-vault feature to backupdr-backupvault (#12239) (#20235)

[upstream:069cde81fbc480835d0a37637460995cdbab1e1e]

Signed-off-by: Modular Magician <[email protected]>

Author: modular-magician

.changelog/12239.txt

@@ -0,0 +1,3 @@
+```release-note: enhancement
+backupdr: added `access_restriction` field to`google_backup_dr_backup_vault` resource (beta)
+```

website/docs/r/backup_dr_backup_vault.html.markdown

@@ -44,6 +44,7 @@ resource "google_backup_dr_backup_vault" "backup-vault-test" {
     annotations2 = "baz1"
   }
   force_update = "true"
+  access_restriction = "WITHIN_ORGANIZATION"
   ignore_inactive_datasources = "true"
   ignore_backup_plan_references = "true"
   allow_missing = "true"
@@ -92,6 +93,12 @@ The following arguments are supported:
   **Note**: This field is non-authoritative, and will only manage the annotations present in your configuration.
   Please refer to the field `effective_annotations` for all of the annotations present on the resource.
 
+* `access_restriction` -
+  (Optional)
+  Access restriction for the backup vault. Default value is `WITHIN_ORGANIZATION` if not provided during creation.
+  Default value is `WITHIN_ORGANIZATION`.
+  Possible values are: `ACCESS_RESTRICTION_UNSPECIFIED`, `WITHIN_PROJECT`, `WITHIN_ORGANIZATION`, `UNRESTRICTED`, `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA`.
+
 * `force_update` -
   (Optional)
   If set, allow update to extend the minimum enforced retention for backup vault. This overrides