Important Changes (Repeat - Reminder)
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.profilebuiltin:appsec.notification-alerting-profilebuiltin:failure-detection.environment.rulesbuiltin:service-detection.external-web-requestbuiltin:service-detection.external-web-servicebuiltin:service-detection.full-web-requestbuiltin:service-detection.full-web-service
Bug Fixes
- #426 - Running the export functionality with an invalid API Token can crash the utility
- #427 - Unnecessary additional HTTP traffic (required for resources supporting the attribute
insert_after) for almost all resources
Improvements
- Introduced the environment variable
DT_BACKWARDS_COMPATIBILITY. A set of attributes and resource blocks will be treated asoptionalin this case, even when they are normally flagged asrequired. Use case: Migrating Settings from very outdated Dynatrace Clusters to new Environments.