v1.42.0

Author: Reinhard-Pilz-Dynatrace

docs/guides/environment-migration.md

@@ -55,6 +55,12 @@ Most resources do not allow configuration with the same name, but there is a sma
 * `DYNATRACE_DUPLICATE_REJECT=ALL` - Duplicates will not overwrite existing configuration
 * `DYNATRACE_DUPLICATE_HIJACK=ALL` - Duplicates will overwrite existing configuration
 
+A common approach with the configuration migration is to do an apply prior to the OneAgent migration and then a reapply after to deploy any configuration that depend on entities existing. An underlying dependency which has entity verification could have cascading effects where a data source could be driven to `null` and the plan/apply prevents execution. 
+
+Example: You may have a request attribute which has an entity filter, a calculated service metric that depends on this request attribute, and a dashboard that is using the calculated service metric. 
+
+In order to have a successful execution, the environment variable `MIGRATION=true` can be set which will replace `null` data source references with a name prefixed with `TFMIGRATIONID-`. This feature is currently available for calculated service metric and SLO data sources. When enabling this feature, a log file will be produced which will contain all resources that are incomplete due to missing underlying dependencies. Reapplying the configuration once the underlying resource dependency exists will automatically repair any resources.
+
 For an iterative migration, utilize the `-migrate -datasources` flags. This will create all of the necessary files with dependencies via data sources and hardcoded entity IDs.
 
 Windows: `terraform-provider-dynatrace.exe -export -migrate -datasources <resourcename>`

docs/index.md

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

docs/resources/calculated_synthetic_metric.md

@@ -30,7 +30,7 @@ resource "dynatrace_calculated_synthetic_metric" "#name#" {
   enabled            = true
   metric             = "ResourceCount"
   metric_key         = "calc:synthetic.browser.#name#"
-  monitor_identifier = "SYNTHETIC_TEST-74EEC98A3855C3DD"
+  monitor_identifier = "SYNTHETIC_TEST-147CFF44DDB25C05"
 }
 ```
 

docs/resources/log_timestamp.md

@@ -53,6 +53,7 @@ resource "dynatrace_log_timestamp" "#name#" {
 
 ### Optional
 
+- `date_search_limit` (Number) (v1.275) Defines the number of characters in every log line (starting from the first character in the line) where the timestamp is searched.
 - `matchers` (Block List, Max: 1) no documentation available (see [below for nested schema](#nestedblock--matchers))
 - `scope` (String) The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
 

docs/resources/slo_v2.md

@@ -53,7 +53,6 @@ resource "dynatrace_slo_v2" "#name#" {
 - `evaluation_window` (String) Define the timeframe during which the SLO is to be evaluated. For the timeframe you can enter expressions like -1h (last hour), -1w (last week) or complex expressions like -2d to now (last two days), -1d/d to now/d (beginning of yesterday to beginning of today).
 - `filter` (String) Set a filter parameter (entitySelector) on any GET call to evaluate this SLO against specific services only (for example, type("SERVICE")).  For details, see the [Entity Selector documentation](https://dt-url.net/entityselector).
 - `metric_expression` (String) For details, see the [Metrics page](/ui/metrics "Metrics page").
-- `metric_name` (String) Metric name
 - `name` (String) SLO name
 - `target_success` (Number) Set the target value of the SLO. A percentage below this value indicates a failure.
 - `target_warning` (Number) Set the warning value of the SLO. At the warning state the SLO is fulfilled. However, it is getting close to a failure.
@@ -62,6 +61,7 @@ resource "dynatrace_slo_v2" "#name#" {
 
 - `custom_description` (String) The description of the SLO
 - `legacy_id` (String) The ID of this setting when referred to by the Config REST API V1
+- `metric_name` (String) Metric name
 
 ### Read-Only
 

docs/resources/unified_services_metrics.md

@@ -0,0 +1,48 @@
+---
+layout: ""
+page_title: dynatrace_unified_services_metrics Resource - terraform-provider-dynatrace"
+subcategory: "Service Detection"
+description: |-
+  The resource `dynatrace_unified_services_metrics` allows to enable/disable endpoint metrics for Unified services
+---
+
+# dynatrace_unified_services_metrics (Resource)
+
+-> This resource requires the API token scopes **Read settings** (`settings.read`) and **Write settings** (`settings.write`)
+
+## Dynatrace Documentation
+
+- Unified service - https://www.dynatrace.com/support/help/platform-modules/applications-and-microservices/services/service-detection-and-naming/service-types/unified-service
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:unified-services-endpoint-metrics`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_unified_services_metrics` downloads existing unified services endpoint metrics 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_unified_services_metrics" "#name#" {
+  enable_endpoint_metrics = true
+  service_id              = "environment"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `enable_endpoint_metrics` (Boolean) Should metrics be written for endpoints? Please be aware that this setting has billing implications. Check out this [documentation](https://dt-url.net/td23cgh) for further details.
+
+### Optional
+
+- `service_id` (String) The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+ 

docs/resources/unified_services_opentel.md

@@ -0,0 +1,43 @@
+---
+layout: ""
+page_title: dynatrace_unified_services_opentel Resource - terraform-provider-dynatrace"
+subcategory: "Service Detection"
+description: |-
+  The resource `dynatrace_unified_services_opentel` allows to enable/disable unified services for OpenTelemetry
+---
+
+# dynatrace_unified_services_opentel (Resource)
+
+-> This resource requires the API token scopes **Read settings** (`settings.read`) and **Write settings** (`settings.write`)
+
+## Dynatrace Documentation
+
+- Unified service - https://www.dynatrace.com/support/help/platform-modules/applications-and-microservices/services/service-detection-and-naming/service-types/unified-service
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:unified-services-enablement`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_unified_services_opentel` downloads existing unified services OpenTelemetry 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_unified_services_opentel" "#name#" {
+  enabled = true
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+ 

provider/version/version.go

@@ -17,4 +17,4 @@
 
 package version
 
-const Current = "1.41.0"
+const Current = "1.42.0"

templates/index.md.tmpl

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