Generated documentation prior to releasing v1.22.0

Author: Reinhard-Pilz-Dynatrace

docs/data-sources/alerting_profile.md

@@ -39,4 +39,5 @@ resource "dynatrace_webhook_notification" "my_webhook_notification" {
 
 ### Read-Only
 
-- `id` (String) The ID of this resource.
+- `id` (String) The ID of this resource.
+- `legacy_id` (String)

docs/data-sources/management_zone.md

@@ -53,4 +53,5 @@ resource "dynatrace_calculated_service_metric" "#name#" {
 ### Read-Only
 
 - `id` (String) The ID of this resource.
+- `legacy_id` (String)
 - `settings_20_id` (String)

docs/index.md

@@ -18,7 +18,7 @@ Use the links to the left to learn about the available resources and data source
 terraform {
     required_providers {
         dynatrace = {
-            version = "1.21.0"
+            version = "1.22.0"
             source = "dynatrace-oss/dynatrace"
         }
     }

docs/resources/aws_credentials.md

@@ -66,11 +66,14 @@ Optional:
 
 - `access_key` (String) the access key
 - `account_id` (String) the ID of the Amazon account
-- `external_id` (String) the external ID token for setting an IAM role. You can obtain it with the `GET /aws/iamExternalId` request
 - `iam_role` (String) the IAM role to be used by Dynatrace to get monitoring data
 - `secret_key` (String, Sensitive) the secret access key
 - `unknowns` (String) Any attributes that aren't yet supported by this provider
 
+Read-Only:
+
+- `external_id` (String) (Read only) the external ID token for setting an IAM role. You can obtain it with the `GET /aws/iamExternalId` request
+
 
 <a id="nestedblock--supporting_services_to_monitor"></a>
 ### Nested Schema for `supporting_services_to_monitor`

docs/resources/browser_monitor.md

@@ -7,6 +7,8 @@ description: |-
 
 # dynatrace_browser_monitor (Resource)
 
+-> Certain field(s) of this resource has overlap with `dynatrace_browser_monitor_outage`, please review the schema for additional information.
+
 ## Dynatrace Documentation
 
 - Synthetic Monitoring - Browser monitors - https://www.dynatrace.com/support/help/shortlink/synthetic-hub#browser-monitors
@@ -231,15 +233,15 @@ Optional:
 
 Optional:
 
-- `global_outage` (Boolean) When enabled (`true`), generate a problem and send an alert when the monitor is unavailable at all configured locations
-- `global_outage_policy` (Block List) Global outage handling configuration. 
+- `global_outage` (Boolean) (Field has overlap with `dynatrace_browser_monitor_outage` and `dynatrace_http_monitor_outage`) When enabled (`true`), generate a problem and send an alert when the monitor is unavailable at all configured locations
+- `global_outage_policy` (Block List) (Field has overlap with `dynatrace_browser_monitor_outage` and `dynatrace_http_monitor_outage`) Global outage handling configuration. 
 
  Alert if **consecutiveRuns** times consecutively (see [below for nested schema](#nestedblock--anomaly_detection--outage_handling--global_outage_policy))
-- `local_outage` (Boolean) When enabled (`true`), generate a problem and send an alert when the monitor is unavailable for one or more consecutive runs at any location
-- `local_outage_policy` (Block List) Local outage handling configuration. 
+- `local_outage` (Boolean) (Field has overlap with `dynatrace_browser_monitor_outage` and `dynatrace_http_monitor_outage`) When enabled (`true`), generate a problem and send an alert when the monitor is unavailable for one or more consecutive runs at any location
+- `local_outage_policy` (Block List) (Field has overlap with `dynatrace_browser_monitor_outage` and `dynatrace_http_monitor_outage`) Local outage handling configuration. 
 
  Alert if **affectedLocations** of locations are unable to access the web application **consecutiveRuns** times consecutively (see [below for nested schema](#nestedblock--anomaly_detection--outage_handling--local_outage_policy))
-- `retry_on_error` (Boolean) Schedule retry if browser monitor execution results in a fail. For HTTP monitors this property is ignored
+- `retry_on_error` (Boolean) (Field has overlap with `dynatrace_browser_monitor_outage` and `dynatrace_http_monitor_outage`) Schedule retry if browser monitor execution results in a fail. For HTTP monitors this property is ignored
 
 <a id="nestedblock--anomaly_detection--outage_handling--global_outage_policy"></a>
 ### Nested Schema for `anomaly_detection.outage_handling.global_outage_policy`

docs/resources/browser_monitor_outage.md

@@ -0,0 +1,58 @@
+---
+layout: ""
+page_title: dynatrace_browser_monitor_outage Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_browser_monitor_outage` covers configuration for browser monitor outage handling
+---
+
+# dynatrace_browser_monitor_outage (Resource)
+
+-> **Settings 2.0** Certain field(s) of this resource has overlap with `dynatrace_browser_monitor`, therefore it is excluded from the default export. To retrieve this resource via export, directly specify it as a command line argument. 
+
+## Dynatrace Documentation
+
+- Synthetic alerting overview - https://www.dynatrace.com/support/help/platform-modules/digital-experience/synthetic-monitoring/analysis-and-alerting/synthetic-alerting-overview
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:synthetic.browser.outage-handling`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_browser_monitor_outage` downloads all existing browser monitor outage handling configuration
+
+The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_browser_monitor_outage" "#name#" {
+  global_consecutive_outage_count_threshold = 3
+  global_outages                            = true
+  local_consecutive_outage_count_threshold  = 5
+  local_location_outage_count_threshold     = 1
+  local_outages                             = true
+  retry_on_error                            = true
+  scope                                     = "environment"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `global_outages` (Boolean) (Field has overlap with `dynatrace_browser_monitor`) Generate a problem and send an alert when the monitor is unavailable at all configured locations.
+- `local_outages` (Boolean) (Field has overlap with `dynatrace_browser_monitor`) Generate a problem and send an alert when the monitor is unavailable for one or more consecutive runs at any location.
+- `retry_on_error` (Boolean) (Field has overlap with `dynatrace_browser_monitor`) When enabled, which is the default, failing monitor executions are retried immediately one time to avoid false positives and only the second result is used. When disabled, we use the first result right away.
+Requires ActiveGate version 1.207+ for private locations.
+
+### Optional
+
+- `global_consecutive_outage_count_threshold` (Number) (Field has overlap with `dynatrace_browser_monitor`) Alert if all locations are unable to access my web application
+- `local_consecutive_outage_count_threshold` (Number) (Field has overlap with `dynatrace_browser_monitor`) are unable to access my web application
+- `local_location_outage_count_threshold` (Number) (Field has overlap with `dynatrace_browser_monitor`) Alert if at least
+- `scope` (String) The scope of this setting (SYNTHETIC_TEST). Omit this property if you want to cover the whole environment.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+ 

docs/resources/cloudapp_workloaddetection.md

@@ -0,0 +1,139 @@
+---
+layout: ""
+page_title: "dynatrace_cloudapp_workloaddetection Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_cloudapp_workloaddetection` merges processes of similar workloads into process groups, and consequently, services. Please note that fine-grained process detection rules will still be applied, while ignoring container or platform specific properties.
+---
+
+# dynatrace_cloudapp_workloaddetection (Resource)
+
+
+## Dynatrace Documentation
+
+- Cloud application and workload detection - https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/cloud-app-and-workload-detection
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:process-group.cloud-application-workload-detection`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_cloudapp_workloaddetection` downloads all existing muted requests configuration
+
+The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
+
+## Resource Example Usage
+
+```terraform
+# ID vu9U3hXa3q0AAAABADpidWlsdGluOnByb2Nlc3MtZ3JvdXAuY2xvdWQtYXBwbGljYXRpb24td29ya2xvYWQtZGV0ZWN0aW9uAAZ0ZW5hbnQABnRlbmFudAAkYjcwNmY4NWYtNWFkNC0zY2ZmLWJhYzMtZDg4YzFmNTkzMjgwvu9U3hXa3q0
+resource "dynatrace_cloudapp_workloaddetection" "cloud_app_workload_detection" {
+  cloud_foundry {
+    enabled = false
+  }
+  docker {
+    enabled = true
+  }
+  kubernetes {
+    enabled = true
+    filters {
+      filter {
+        enabled = false
+        inclusion_toggles {
+          inc_basepod   = false
+          inc_container = true
+          inc_namespace = true
+          inc_product   = true
+          inc_stage     = true
+        }
+        match_filter {
+          match_operator = "EXISTS"
+        }
+      }
+    }
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `cloud_foundry` (Block List, Min: 1, Max: 1) Enable this setting to get 
+ * Processes of Cloud Foundry application instances merged into process groups by Cloud Foundry application. 
+ *  Container resource metrics (Container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). (see [below for nested schema](#nestedblock--cloud_foundry))
+- `docker` (Block List, Min: 1, Max: 1) Enable this setting for plain Docker environments to get 
+ * Container resource metrics (Container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). (see [below for nested schema](#nestedblock--docker))
+- `kubernetes` (Block List, Min: 1, Max: 1) Enable this setting to get 
+ * Insights into your Kubernetes namespaces, workloads and pods (cloud application namespace, cloud application and cloud application instance and entities). 
+ * Container resource metrics (container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). 
+ * Similar workloads merged into process groups based on defined rules (see below). 
+ * Version detection for services that run in Kubernetes workloads. (see [below for nested schema](#nestedblock--kubernetes))
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--cloud_foundry"></a>
+### Nested Schema for `cloud_foundry`
+
+Required:
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+
+
+<a id="nestedblock--docker"></a>
+### Nested Schema for `docker`
+
+Required:
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+
+
+<a id="nestedblock--kubernetes"></a>
+### Nested Schema for `kubernetes`
+
+Required:
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+- `filters` (Block List, Min: 1, Max: 1) Define rules to merge similar Kubernetes workloads into process groups. 
+
+ You can use workload properties like namespace name, base pod name or container name as well as the [environment variables DT_RELEASE_STAGE and DT_RELEASE_PRODUCT](https://dt-url.net/sb02v2a) for grouping processes of similar workloads. The first applicable rule will be applied. If no rule matches, “Namespace name” + “Base pod name” + “Container name” is used as fallback. (see [below for nested schema](#nestedblock--kubernetes--filters))
+
+<a id="nestedblock--kubernetes--filters"></a>
+### Nested Schema for `kubernetes.filters`
+
+Required:
+
+- `filter` (Block List, Min: 1) (see [below for nested schema](#nestedblock--kubernetes--filters--filter))
+
+<a id="nestedblock--kubernetes--filters--filter"></a>
+### Nested Schema for `kubernetes.filters.filter`
+
+Required:
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+- `inclusion_toggles` (Block List, Min: 1, Max: 1) ID calculation based on (see [below for nested schema](#nestedblock--kubernetes--filters--filter--inclusion_toggles))
+- `match_filter` (Block List, Min: 1, Max: 1) When namespace (see [below for nested schema](#nestedblock--kubernetes--filters--filter--match_filter))
+
+<a id="nestedblock--kubernetes--filters--filter--inclusion_toggles"></a>
+### Nested Schema for `kubernetes.filters.filter.inclusion_toggles`
+
+Required:
+
+- `inc_basepod` (Boolean) E.g. "cloud-credential-operator-" for "cloud-credential-operator-5ff6dbff57-gszgq"
+- `inc_container` (Boolean) Container name
+- `inc_namespace` (Boolean) Namespace name
+- `inc_product` (Boolean) If Product is enabled and has no value, it defaults to Base pod name
+- `inc_stage` (Boolean) Stage
+
+
+<a id="nestedblock--kubernetes--filters--filter--match_filter"></a>
+### Nested Schema for `kubernetes.filters.filter.match_filter`
+
+Required:
+
+- `match_operator` (String) Possible Values: `CONTAINS`, `ENDS`, `EQUALS`, `EXISTS`, `NOT_CONTAINS`, `NOT_ENDS`, `NOT_EQUALS`, `NOT_STARTS`, `STARTS`
+
+Optional:
+
+- `namespace` (String) Namespace name
+ 

docs/resources/credentials.md

@@ -8,7 +8,7 @@ description: |-
 
 # dynatrace_credentials (Resource)
 
--> In order to create a this resource, your `dt_api_token` needs to have the `Write credential vault entries` permission.
+
 
 
 

docs/resources/dashboard.md

@@ -25,7 +25,6 @@ The full documentation of the export feature is available [here](https://registr
 resource "dynatrace_dashboard" "#name#" {
   dashboard_metadata {
     name   = "#name#"
-    shared = false
     owner  = "Dynatrace"
     tags   = ["Kubernetes"]
     dynamic_filters {
@@ -836,8 +835,8 @@ Optional:
 - `dynamic_filters` (Block List, Max: 1) Dashboard filter configuration of a dashboard (see [below for nested schema](#nestedblock--dashboard_metadata--dynamic_filters))
 - `filter` (Block List, Max: 1) Global filter Settings for the Dashboard (see [below for nested schema](#nestedblock--dashboard_metadata--filter))
 - `preset` (Boolean) the dashboard is a preset (`true`) or not (`false`). Default is `false`.
-- `shared` (Boolean) the dashboard is shared (`true`) or private (`false`)
-- `sharing_details` (Block List, Max: 1) represents sharing configuration of a dashboard (see [below for nested schema](#nestedblock--dashboard_metadata--sharing_details))
+- `shared` (Boolean, Deprecated) the dashboard is shared (`true`) or private (`false`)
+- `sharing_details` (Block List, Max: 1, Deprecated) represents sharing configuration of a dashboard (see [below for nested schema](#nestedblock--dashboard_metadata--sharing_details))
 - `tags` (Set of String) a set of tags assigned to the dashboard
 - `tiles_name_size` (Number) No documentation available
 - `unknowns` (String) allows for configuring properties that are not explicitly supported by the current version of this provider