Important Breaking Changes
Once your Dynatrace Environment has gotten (auto)-updated to v1.280 applying the resources dynatrace_span_attribute and dynatrace_resource_attributes will result with an error message signalling that the old schemata are not valid anymore.
At this point you will have to migrate your modules to use the resources dynatrace_attribute_allow_list and dynatrace_attribute_masking.
Reason for that is a breaking change in the REST API with cluster version 1.280 scheduled to be released in a few days. While we were able to implement an adapter for the resource dynatrace_span_attribute (kudos to @kishikawa12), implementing something similar for dynatrace_resource_attributes unfortunately turned out to be too complex.
New Resources
dynatrace_host_monitoring_advancedcovers advanced configuration for host monitoringdynatrace_attribute_allow_listcovers configuration for OpenTracing and OpenTelemetry attribute allow-listdynatrace_attribute_maskingcovers configuration for OpenTracing and OpenTelemetry attribute masking
Updated Resources
The following resources have been updated to support the most recent schema version offered by the Dynatrace API
dynatrace_process_monitoring_ruledynatrace_host_monitoring
Bug Fixes
- #356 - Attribute has_http_error not handled properly for resource calculated_mobile_metric
- #360 -
dynatrace_auto_tag_v2created plans with empty rules - #359 -
dynatrace_azure_serviceclashed with default services Dynatrace assumes when creatingdynatrace_azure_credentials. The resourcedynatrace_azure_credentialsnow offers an attributeremove_defaultssignalling that any Azure Services Dynatrace creates by default will get removed upon creation. - Updating
dynatrace_network_zonecould potentiall crash the provider because of nil point access