Important Changes
The following resources can result in non-empty plans due to a recent update in the REST API. Starting with v287, the API will return the Settings 2.0 ID of any referenced Management Zone ID of the schemas below instead of the configuration V1 ID that it previously returned. In order to resolve this issue, please update any Management Zone references from legacy_id
to id
. Any hardcoded Management Zone will need to be updated to the Settings 2.0 ID equivalent to result in a non-empty plan.
builtin:alerting.profile
builtin:appsec.notification-alerting-profile
builtin:failure-detection.environment.rules
builtin:service-detection.external-web-request
builtin:service-detection.external-web-service
builtin:service-detection.full-web-request
builtin:service-detection.full-web-service
New Resources
dynatrace_managed_network_zones
covers configuration for Managed cluster network zones
New Data Sources
dynatrace_management_zone_v2
covers queries for the ID of a management zone based on name. This new v2 data source will only require thesettings.read
scope since it is using the Settings 2.0 API. This will be used as the default for Management Zone dependencies in the export utility.
Improvements
- Introduced export capability for
dynatrace_policy_bindings
anddynatrace_mgmz_permission
Schema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_business_events_oneagent
dynatrace_calculated_service_metric
dynatrace_credentials
dynatrace_request_attribute
dynatrace_web_application