dynatrace-oss/terraform-provider-dynatrace v1.12.1 on GitHub

Release v1.12.1 introduces the following Data Sources:

dynatrace_management_zone allows you to query for Management Zones based on Name.
dynatrace_service allows you to query for Topology Services based on Service Name and Tags and Tag/Value Pairs.
dynatrace_host allows you to query for Hosts based on Name and Tags.
dynatrace_processgroup allows you to query for Process Groups based on Name and Tags.
dynatrace_process allows you to query for Processes Groups based on Name and Tags.

Upcoming releases wiil introduce the ability to specify Tag/Value Pairs during query for all of the above mentioned Topology Entities.

The following example shows a Data Source querying for a Service named Requests executed in background threads of Code*Service.exe that has a Tag named TerraformKeyTest with any or no value applied and a Tag named TerraformKeyValueTest with the value TestValue. Both Tags need to be present. If multiple Topology Services are matching the given criteria the first one found will be chosen.

data "dynatrace_service" "Test" {
  name = "Requests executed in background threads of Code*Service.exe"
  tags = ["TerraformKeyTest","TerraformKeyValueTest=TestValue"]
}

The ID of the resolved Toplogy Service can now be referred to within any resource.

resource "dynatrace_key_requests" "TerraformTest" {
  service = data.dynatrace_service.Test.id
}

Changes and fixes for existing Resources and Data Sources:

dynatrace_custom_service now supports the attributes visibility and modifiers officially. These attributes used to be supported via unknowns attribute in the past.
Dashboard Metadata within the Resource dynatrace_dashboard now supports the attribute consistent_colors.
The order of rules within Resource dynatrace_alerting_profile is now getting enforced by the Terraform Provider. This turned out to become necessary because the Dynatrace REST API does not guarantee to deliver them in the same order it has received them. You may have to adjust your HCL files to the order the Provider will choose for you. As a rule of thumb here: The JSON formatted representation of the Rules will be ordered alphabetically.
The order of rules and conditions within Resource dynatrace_management_zone are now getting enforced by the Terraform Provider - for the same reason as for dynatrace_alerting_profile.