doc: Update resource documentation

Author: arthurpitman

docs/index.md

@@ -122,7 +122,7 @@ If `DYNATRACE_HTTP_OAUTH_PREFERENCE` is not set or is not `true`, the provider w
 You can authenticate using a Platform Token by setting the environment variable:
 
 ```
-DYNATRACE_PLATFORM_TOKEN
+DYNATRACE_PLATFORM_TOKEN=<<PLATFORM_TOKEN>>
 ```
 
 Alternatively, you can use the `platform_token` attribute in the provider configuration.

docs/resources/attribute_masking.md

@@ -27,7 +27,7 @@ The full documentation of the export feature is available [here](https://dt-url.
 ```terraform
 resource "dynatrace_attribute_masking" "#name#" {
   enabled = true
-  key = "attribute.example"
+  key = "attribute.#name#"
   masking = "MASK_ENTIRE_VALUE"
 }
 ```

docs/resources/automation_approval.md

@@ -0,0 +1,36 @@
+---
+layout: ""
+page_title:  Resource - terraform-provider-dynatrace"
+subcategory: "Automation"
+description: |-
+  The resource `dynatrace_automation_approval` covers configuration for automation workflow approval
+---
+
+# dynatrace_automation_approval (Resource)
+
+-> This resource requires the API token scopes **Read settings** (`settings.read`) and **Write settings** (`settings.write`)
+
+## Dynatrace Documentation
+
+- Dynatrace Workflows - https://www.dynatrace.com/support/help/platform-modules/cloud-automation/workflows
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:automation.approval)
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_automation_approval" "#name#" {
+  workflow_app_access_approval_enabled = true
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `workflow_app_access_approval_enabled` (Boolean) Allow on tenant level anyone with access to the app can respond to requests via an approval link.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.

docs/resources/automation_workflow.md

@@ -229,7 +229,7 @@ Optional:
 
 Optional:
 
-- `entity_tags` (Map of String) key/value pairs for entity tags to match for. For tags that don't require a value, just specify an empty string as value. Omit this attribute if all entities should match
+- `entity_tags` (Map of String) key/value pairs for entity tags to match for. For tags that don't require a value, just specify an empty string as value. Multiple values can be provided separated by whitespace (e.g. "val1 val2") and will be parsed as multiple tag values. Omit this attribute if all entities should match
 - `entity_tags_match` (String) Specifies whether all or just any of the configured entity tags need to match. Possible values: `all` and `any`. Omit this attribute if all entities should match
 - `names` (Block List, Max: 1) The Davis Events to match on (see [below for nested schema](#nestedblock--trigger--event--config--davis_event--names))
 - `on_problem_close` (Boolean) If set to `true` closing a problem also is considered an event that triggers the execution
@@ -263,7 +263,7 @@ Required:
 Optional:
 
 - `custom_filter` (String)
-- `entity_tags` (Map of String) key/value pairs for entity tags to match for. For tags that don't require a value, just specify an empty string as value. Omit this attribute if all entities should match
+- `entity_tags` (Map of String) key/value pairs for entity tags to match for. For tags that don't require a value, just specify an empty string as value. Multiple values can be provided separated by whitespace (e.g. "val1 val2") and will be parsed as multiple tag values. Omit this attribute if all entities should match
 - `entity_tags_match` (String) Specifies whether all or just any of the configured entity tags need to match. Possible values: `all` and `any`. Omit this attribute if all entities should match
 - `on_problem_close` (Boolean) If set to `true` closing a problem also is considered an event that triggers the execution
 

docs/resources/aws_service.md

@@ -16,16 +16,15 @@ description: |-
 
 - Amazon Web Services - https://www.dynatrace.com/support/help/setup-and-configuration/setup-on-cloud-platforms/amazon-web-services/amazon-web-services-integrations/aws-service-metrics
 
+- The dimensions and statistics for metrics for individual services - https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/aws-all-services
+
 - AWS credentials API - https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/aws-credentials-api
 
 ## Resource Example Usage
 
 This example utilizes the data source `dynatrace_aws_supported_services` in order to query for a full list of all supported services.
 The `for_each` loop within the resource `dynatrace_aws_service` configures each of these services to get utilized with the default metrics recommended by Dynatrace (`use_recommended_metrics`).
 
-If you want to configure a different set of metrics for a specific service, a separate resource `dynatrace_aws_service` will be necessary for that. That allows you to configure the `metric` blocks according to your wishes.
-Just be aware of the fact, that Dynatrace enforces for most services a recommended set of metrics. All of them need to be part of your configuration in order to end up with a non-empty plan.
-
 ```terraform
 resource "dynatrace_aws_credentials" "TERRAFORM_SAMPLE" {
   label          = "TERRAFORM-TEST-001"
@@ -49,12 +48,42 @@ resource "dynatrace_aws_service" "TERRAFORM_SAMPLE_services" {
 }
 ```
 
+If you want to configure a different set of metrics for a specific service, a separate resource `dynatrace_aws_service` will be necessary for that. That allows you to configure the `metric` blocks according to your wishes.
+Just be aware of the fact, that Dynatrace enforces for most services a recommended set of metrics. All of them need to be part of your configuration in order to end up with a non-empty plan.
+
+```terraform
+resource "dynatrace_aws_credentials" "Example" {
+  label                                 = "#name#"
+  partition_type                        = "AWS_DEFAULT"
+  tagged_only                           = false
+  authentication_data {
+    account_id = "123456789"
+    iam_role   = "aws-monitoring-role"
+  }
+}
+
+resource "dynatrace_aws_service" "ElastiCache" {
+  name           = "ElastiCache"
+  credentials_id = dynatrace_aws_credentials.Example.id
+  metric {
+    name       = "NetworkBandwidthOutAllowanceExceeded"
+    dimensions = [ "CacheClusterId" ]
+    statistic  = "SUM"
+  }
+  metric {
+    name       = "CPUUtilization"
+    dimensions = [ "CacheClusterId" ]
+    statistic  = "AVG_MIN_MAX"
+  }
+}
+```
+
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
 ### Required
 
-- `credentials_id` (String) the ID of the azure credentials this supported service belongs to
+- `credentials_id` (String) the ID of the AWS credentials this supported service belongs to
 
 ### Optional
 
@@ -73,10 +102,10 @@ resource "dynatrace_aws_service" "TERRAFORM_SAMPLE_services" {
 
 Required:
 
+- `dimensions` (List of String) a list of metric's dimensions names
 - `name` (String) the name of the metric of the supporting service
 
 Optional:
 
-- `dimensions` (List of String) a list of metric's dimensions names
 - `statistic` (String) Possible values are `AVERAGE`, `AVG_MIN_MAX`, `MAXIMUM`, `MINIMUM`, `SAMPLE_COUNT` and `SUM`
 

docs/resources/azure_service.md

@@ -16,16 +16,15 @@ description: |-
 
 - Microsoft Azure monitoring - https://www.dynatrace.com/support/help/how-to-use-dynatrace/infrastructure-monitoring/cloud-platform-monitoring/microsoft-azure-services-monitoring
 
+- The dimensions for metrics for individual services - https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-cloud-services-metrics
+
 - Azure credentials API - https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/azure-credentials-api
 
 ## Resource Example Usage
 
 This example utilizes the data source `dynatrace_azure_supported_services` in order to query for a full list of all supported services.
 The `for_each` loop within the resource `dynatrace_azure_service` configures each of these services to get utilized with the default metrics recommended by Dynatrace (`use_recommended_metrics`).
 
-If you want to configure a different set of metrics for a specific service, a separate resource `dynatrace_azure_service` will be necessary for that. That allows you to configure the `metric` blocks according to your wishes.
-Just be aware of the fact, that Dynatrace enforces for most services a recommended set of metrics. All of them need to be part of your configuration in order to end up with a non-empty plan.
-
 ```terraform
 resource "dynatrace_azure_credentials" "TERRAFORM_SAMPLE" {
   active                       = false
@@ -54,12 +53,45 @@ resource "dynatrace_azure_service" "TERRAFORM_SAMPLE_services" {
 }
 ```
 
+If you want to configure a different set of metrics for a specific service, a separate resource `dynatrace_azure_service` will be necessary for that. That allows you to configure the `metric` blocks according to your wishes.
+Just be aware of the fact, that Dynatrace enforces for most services a recommended set of metrics. All of them need to be part of your configuration in order to end up with a non-empty plan.
+
+```terraform
+resource "dynatrace_azure_credentials" "Example" {
+  active                                     = true
+  app_id                                     = "123456789"
+  auto_tagging                               = true
+  directory_id                               = "123456789"
+  key                                        = "123456789"
+  label                                      = "#name#"
+  monitor_only_tagged_entities               = false
+}
+
+
+resource "dynatrace_azure_service" "ContainerService" {
+  name           = "cloud:azure:containerservice:managedcluster"
+  credentials_id = dynatrace_azure_credentials.Example.id
+  metric {
+    name = "kube_pod_status_ready"
+    dimensions = []
+  }
+  metric {
+    name       = "kube_node_status_condition"
+    dimensions = [ "condition", "status", "node" ]
+  }
+  metric {
+    name       = "kube_pod_status_phase"
+    dimensions = [ "phase", "namespace" ]
+  }
+}
+```
+
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
 ### Required
 
-- `credentials_id` (String) the ID of the azure credentials this supported service belongs to
+- `credentials_id` (String) the ID of the Azure credentials this supported service belongs to
 
 ### Optional
 

docs/resources/document.md

@@ -24,6 +24,7 @@ description: |-
 resource "dynatrace_document" "this" {
   type = "dashboard"
   name = "Example Dashboard"
+  custom_id = "#name#"
   content = jsonencode(
     {
       "version" : 13,
@@ -177,11 +178,11 @@ resource "dynatrace_document" "this" {
 
 ### Optional
 
-- `actor` (String) The user context the executions of the document will happen with
-- `owner` (String) The ID of the owner of this document
+- `custom_id` (String) If provided, this will be the id of the document. If not provided, a system-generated id is used.
 - `private` (Boolean) Specifies whether the document is private or readable by everybody
 
 ### Read-Only
 
 - `id` (String) The ID of this resource.
+- `owner` (String) The ID of the owner of this document
 - `version` (Number) The version of the document

docs/resources/hub_subscriptions.md

@@ -28,7 +28,7 @@ The full documentation of the export feature is available [here](https://dt-url.
 resource "dynatrace_hub_subscriptions" "#name#" {
   token_subscriptions {
     token_subscription {
-      name        = "#name"
+      name        = "#name#"
       description = "Description"
       enabled     = true
       token       = "123456789012345678901234567890123456"

docs/resources/openpipeline_v2_bizevents_ingestsources.md

@@ -158,7 +158,7 @@ Required:
 - `description` (String) no documentation available
 - `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
 - `id` (String) Processor identifier
-- `type` (String) Possible Values: `AzureLogForwarding`, `Bizevent`, `BucketAssignment`, `CostAllocation`, `CounterMetric`, `Davis`, `Dql`, `Drop`, `FieldsAdd`, `FieldsRemove`, `FieldsRename`, `HistogramMetric`, `NoStorage`, `ProductAllocation`, `SamplingAwareCounterMetric`, `SamplingAwareValueMetric`, `SecurityContext`, `SecurityEvent`, `Technology`, `ValueMetric`
+- `type` (String) Processor type. Possible Values: `azureLogForwarding`, `bizevent`, `bucketAssignment`, `costAllocation`, `counterMetric`, `davis`, `dql`, `drop`, `fieldsAdd`, `fieldsRemove`, `fieldsRename`, `histogramMetric`, `noStorage`, `productAllocation`, `samplingAwareCounterMetric`, `samplingAwareValueMetric`, `securityContext`, `securityEvent`, `technology`, `valueMetric`.
 
 Optional:
 
@@ -196,7 +196,7 @@ Required:
 
 Required:
 
-- `type` (String) Possible Values: `Exclude`, `Include`, `IncludeAll`
+- `type` (String) Fields Extraction type. Possible Values: `exclude`, `include`, `includeAll`.
 
 Optional:
 
@@ -243,7 +243,7 @@ Optional:
 
 Required:
 
-- `type` (String) Possible Values: `Constant`, `Field`, `MultiValueConstant`
+- `type` (String) Type of value assignment. Possible Values: `constant`, `field`, `multiValueConstant`.
 
 Optional:
 
@@ -269,7 +269,7 @@ Optional:
 
 Required:
 
-- `type` (String) Possible Values: `Exclude`, `Include`, `IncludeAll`
+- `type` (String) Fields Extraction type. Possible Values: `exclude`, `include`, `includeAll`.
 
 Optional:
 
@@ -303,7 +303,7 @@ Optional:
 
 Required:
 
-- `type` (String) Possible Values: `Constant`, `Field`, `MultiValueConstant`
+- `type` (String) Type of value assignment. Possible Values: `constant`, `field`, `multiValueConstant`.
 
 Optional:
 
@@ -345,7 +345,7 @@ Required:
 
 Required:
 
-- `type` (String) Possible Values: `Constant`, `Field`, `MultiValueConstant`
+- `type` (String) Type of value assignment. Possible Values: `constant`, `field`, `multiValueConstant`.
 
 Optional:
 
@@ -537,7 +537,7 @@ Required:
 
 Required:
 
-- `type` (String) Possible Values: `Constant`, `Field`, `MultiValueConstant`
+- `type` (String) Type of value assignment. Possible Values: `constant`, `field`, `multiValueConstant`.
 
 Optional:
 
@@ -568,9 +568,9 @@ Required:
 
 Optional:
 
-- `aggregation` (String) Possible Values: `Disabled`, `Enabled`
+- `aggregation` (String) Possible Values: `disabled`, `enabled`.
 - `dimensions` (Block List, Max: 1) List of dimensions (see [below for nested schema](#nestedblock--processing--processors--processor--sampling_aware_counter_metric--dimensions))
-- `sampling` (String) Possible Values: `Disabled`, `Enabled`
+- `sampling` (String) Possible Values: `disabled`, `enabled`.
 
 <a id="nestedblock--processing--processors--processor--sampling_aware_counter_metric--dimensions"></a>
 ### Nested Schema for `processing.processors.processor.sampling_aware_counter_metric.dimensions`
@@ -599,16 +599,16 @@ Optional:
 
 Required:
 
-- `measurement` (String) Possible Values: `Duration`, `Field`
+- `measurement` (String) Possible Values: `duration`, `field`.
 - `metric_key` (String) Metric key
 
 Optional:
 
-- `aggregation` (String) Possible Values: `Disabled`, `Enabled`
+- `aggregation` (String) Possible Values: `disabled`, `enabled`.
 - `default_value` (String) Default value with metric value
 - `dimensions` (Block List, Max: 1) List of dimensions (see [below for nested schema](#nestedblock--processing--processors--processor--sampling_aware_value_metric--dimensions))
 - `field` (String) Field with metric value
-- `sampling` (String) Possible Values: `Disabled`, `Enabled`
+- `sampling` (String) Possible Values: `disabled`, `enabled`.
 
 <a id="nestedblock--processing--processors--processor--sampling_aware_value_metric--dimensions"></a>
 ### Nested Schema for `processing.processors.processor.sampling_aware_value_metric.dimensions`
@@ -644,7 +644,7 @@ Required:
 
 Required:
 
-- `type` (String) Possible Values: `Constant`, `Field`, `MultiValueConstant`
+- `type` (String) Type of value assignment. Possible Values: `constant`, `field`, `multiValueConstant`.
 
 Optional:
 
@@ -678,7 +678,7 @@ Required:
 
 Required:
 
-- `type` (String) Possible Values: `Exclude`, `Include`, `IncludeAll`
+- `type` (String) Fields Extraction type. Possible Values: `exclude`, `include`, `includeAll`.
 
 Optional:
 
@@ -763,7 +763,7 @@ Optional:
 
 Required:
 
-- `pipeline_type` (String) Possible Values: `Builtin`, `Custom`
+- `pipeline_type` (String) Pipeline Type. Possible Values: `builtin`, `custom`.
 
 Optional: