Docs: Fix incorrect properties (#19864)

hashicorp · Jan 5, 2023 · a961507 · a961507
1 parent fc911ab
commit a961507
Show file tree

Hide file tree

Showing 8 changed files with 13 additions and 10 deletions.
diff --git a/website/docs/r/billing_account_cost_management_export.html.markdown b/website/docs/r/billing_account_cost_management_export.html.markdown
@@ -64,7 +64,7 @@ The following arguments are supported:
 
 * `recurrence_period_start_date` - (Required) The date the export will start capturing information.
 
-* `recurrence_period_end` - (Required) The date the export will stop capturing information.
+* `recurrence_period_end_date` - (Required) The date the export will stop capturing information.
 
 * `export_data_storage_location` - (Required) A `export_data_storage_location` block as defined below.
 

diff --git a/website/docs/r/confidential_ledger.html.markdown b/website/docs/r/confidential_ledger.html.markdown
@@ -44,13 +44,13 @@ The following arguments are supported:
 
 * `location` - (Required) Specifies the supported Azure location where the Confidential Ledger exists. Changing this forces a new resource to be created.
 
-* `azuread_service_principal` - (Required) A list of `azuread_service_principal` blocks as defined below.
+* `azuread_based_service_principal` - (Required) A list of `azuread_based_service_principal` blocks as defined below.
 
 * `ledger_type` - (Required) Specifies the type of Confidential Ledger. Possible values are `Private` and `Public`. Changing this forces a new resource to be created.
 
 ---
 
-* `cert_based_security_principals` - (Optional) A list of `cert_based_security_principals` blocks as defined below.
+* `certificate_based_security_principal` - (Optional) A list of `certificate_based_security_principal` blocks as defined below.
 
 * `tags` - (Optional) A mapping of tags to assign to the Confidential Ledger.
 

diff --git a/website/docs/r/cosmosdb_mongo_collection.html.markdown b/website/docs/r/cosmosdb_mongo_collection.html.markdown
@@ -47,6 +47,7 @@ The following arguments are supported:
 
 * `name` - (Required) Specifies the name of the Cosmos DB Mongo Collection. Changing this forces a new resource to be created.
 * `resource_group_name` - (Required) The name of the resource group in which the Cosmos DB Mongo Collection is created. Changing this forces a new resource to be created.
+* `account_name` - (Required) The name of the Cosmos DB Account in which the Cosmos DB Mongo Collection is created. Changing this forces a new resource to be created.
 * `database_name` - (Required) The name of the Cosmos DB Mongo Database in which the Cosmos DB Mongo Collection is created. Changing this forces a new resource to be created.
 * `shard_key` - (Optional) The name of the key to partition on for sharding. There must not be any other unique index keys. Changing this forces a new resource to be created.
 * `analytical_storage_ttl` - (Optional) The default time to live of Analytical Storage for this Mongo Collection. If present and the value is set to `-1`, it is equal to infinity, and items don’t expire by default. If present and the value is set to some number `n` – items will expire `n` seconds after their last modified time.

diff --git a/website/docs/r/log_analytics_cluster.html.markdown b/website/docs/r/log_analytics_cluster.html.markdown
@@ -71,8 +71,6 @@ In addition to the Arguments listed above - the following Attributes are exporte
 
 * `cluster_id` - The GUID of the cluster.
 
-* `type` - The type of the resource. Ex- Microsoft.Compute/virtualMachines or Microsoft.Storage/storageAccounts.
-
 ---
 
 An `identity` block exports the following:

diff --git a/website/docs/r/netapp_snapshot_policy.html.markdown b/website/docs/r/netapp_snapshot_policy.html.markdown
@@ -80,6 +80,8 @@ The following arguments are supported:
 
 * `monthly_schedule` - (Optional) Sets a monthly snapshot schedule. See details in below `monthly_schedule` block.
 
+* `tags` - (Optional) A mapping of tags to assign to the resource.
+
 ---
 
 An `hourly_schedule` block supports the following:
@@ -112,11 +114,11 @@ A `weekly_schedule` block supports the following:
 
 ---
 
-A `weekly_schedule` block supports the following:
+A `monthly_schedule` block supports the following:
 
 * `snapshots_to_keep` - (Required) How many hourly snapshots to keep, valid range is from 0 to 255.
 
-* `monthly_schedule` - (Required) List of the days of the month when the snapshots will be created, valid range is from 1 to 30.
+* `days_of_month` - (Required) List of the days of the month when the snapshots will be created, valid range is from 1 to 30.
 
 * `hour` - (Required) Hour of the day that the snapshots will be created, valid range is from 0 to 23.
 

diff --git a/website/docs/r/netapp_volume.html.markdown b/website/docs/r/netapp_volume.html.markdown
@@ -116,6 +116,8 @@ The following arguments are supported:
 
 * `service_level` - (Required) The target performance of the file system. Valid values include `Premium`, `Standard`, or `Ultra`. Changing this forces a new resource to be created.
 
+* `azure_vmware_data_store_enabled` - (Optional) Is the NetApp Volume enabled for Azure VMware Solution (AVS) datastore purpose. Defaults to `false`. Changing this forces a new resource to be created.
+
 * `protocols` - (Optional) The target volume protocol expressed as a list. Supported single value include `CIFS`, `NFSv3`, or `NFSv4.1`. If argument is not defined it will default to `NFSv3`. Changing this forces a new resource to be created and data will be lost. Dual protocol scenario is supported for CIFS and NFSv3, for more information, please refer to [Create a dual-protocol volume for Azure NetApp Files](https://docs.microsoft.com/azure/azure-netapp-files/create-volumes-dual-protocol) document.
 
 * `security_style` - (Optional) Volume security style, accepted values are `Unix` or `Ntfs`. If not provided, single-protocol volume is created defaulting to `Unix` if it is `NFSv3` or `NFSv4.1` volume, if `CIFS`, it will default to `Ntfs`. In a dual-protocol volume, if not provided, its value will be `Ntfs`. Changing this forces a new resource to be created.

diff --git a/website/docs/r/service_fabric_cluster.html.markdown b/website/docs/r/service_fabric_cluster.html.markdown
@@ -165,7 +165,7 @@ A `client_certificate_common_name` block supports the following:
 
 * `common_name` - (Required) The common or subject name of the certificate.
 
-* `certificate_issuer_thumbprint` - (Optional) The Issuer Thumbprint of the Certificate.
+* `issuer_thumbprint` - (Optional) The Issuer Thumbprint of the Certificate.
 
 -> **NOTE:** Certificate Issuer Thumbprint may become required in the future, `https://docs.microsoft.com/azure/service-fabric/service-fabric-create-cluster-using-cert-cn#download-and-update-a-sample-template`.
 
@@ -243,7 +243,7 @@ A `ephemeral_ports` block supports the following:
 
 A `upgrade_policy` block supports the following:
 
-* `force_restart` - (Optional) Indicates whether to restart the Service Fabric node even if only dynamic configurations have changed.
+* `force_restart_enabled` - (Optional) Indicates whether to restart the Service Fabric node even if only dynamic configurations have changed.
 
 * `health_check_retry_timeout` - (Optional) Specifies the duration, in "hh:mm:ss" string format, after which Service Fabric retries the health check if the previous health check fails. Defaults to `00:45:00`.
 

diff --git a/website/docs/r/subscription_cost_management_export.html.markdown b/website/docs/r/subscription_cost_management_export.html.markdown
@@ -65,7 +65,7 @@ The following arguments are supported:
 
 * `recurrence_period_start_date` - (Required) The date the export will start capturing information.
 
-* `recurrence_period_end` - (Required) The date the export will stop capturing information.
+* `recurrence_period_end_date` - (Required) The date the export will stop capturing information.
 
 * `export_data_storage_location` - (Required) A `export_data_storage_location` block as defined below.