v1.48.1

Bug Fixes

• #384 - The documentation for dynatrace_alerting contained an outdated set of possible operators for text filters
• #382 - Creating a resource dynatrace_platform_bucket returned too early with success - before the whole Dynatrace Cluster was aware of the bucket
• #383 - Updated and corrected the example in the documentation for dynatrace_aws_service

v1.48.0

New Resources and Data Sources

• The data source dynatrace_remote_environments covers queries for remote environments

Important Changes

The resource dynatrace_aws_credentials cannot get used anymore for managing supported services. The block supported_services_to_monitor is still supported but will be ignored. In order to manage supported services the resource dynatrace_aws_service needs to get used from now on. The attribute remove_defaults is still available - signalling to Terraform that any services Dynatrace assigns by default to these credentials will get purged upon creation. Subsequent updates won't be affected by remove_defaults, though.

Bug Fixes

• #372 - Exporting dynatrace_log_processing containing %{if content was not possible
• #370 - Export for dynatrace_iam_policy and dynatrace_iam_policy_bindings found not entries
• #371 - HTTP 400 from API when applying a Workflow with CRON trigger
• #373 - dynatrace_automation_workflow didn't take the attribute private = false into consideration
• #380 - Documentation for dynatrace_pg_alerting incomplete

Improvements

• #374 - dynatrace_credentials now supports the attribute scope and scopes (introduced by REST API 1.281)
• #377 - Data Source dynatrace_entities now populates the attribute last_seen_tms for every entity in order to allow for predictable sorting

Schema Updates

The following resources got updated to be compatible with the most recent schema version of Dynatrace:

• dynatrace_webhook_notification
• dynatrace_log_metrics
• dynatrace_log_oneagent
• dynatrace_builtin_process_monitoring
• dynatrace_oneagent_side_masking
• dynatrace_hub_subscriptions
• dynatrace_mobile_notifications
• dynatrace_request_attribute
• dynatrace_trello_notification
• dynatrace_webhook_notification

v1.47.3

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.

Bug Fixes

• #363 - Timing issue when applying application_detection_rule_v2 after dynatrace_web_application
• #317 - dynatrace_aws_credentials now allows for removing the default services applied during creation
• #369 - Flagging a Dashboard as Preset can result in the resource dynatrace_dashboard_sharing to not apply changes anymore
• Turning on HTTP traffic debug logging for dynatrace_automation_workflow can result in provider crash during oAuth negotiation

v1.47.2

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.

Bug Fixes

• #363 - Timing issue when applying application_detection_rule_v2 after dynatrace_web_application
• #317 - dynatrace_aws_credentials now allows for removing the default services applied during creation
• #369 - Flagging a Dashboard as Preset can result in the resource dynatrace_dashboard_sharing to not apply changes anymore
• Turning on HTTP traffic debug logging for dynatrace_automation_workflow can result in provider crash during oAuth negotiation

v1.47.1

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.

Bug Fixes

• #357/#362 - Applying Supported Services within dynatrace_aws_credentials could lead to non-empty plan containing erroneous empty blocks

v1.47.0

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_advanced covers advanced configuration for host monitoring
• dynatrace_attribute_allow_list covers configuration for OpenTracing and OpenTelemetry attribute allow-list
• dynatrace_attribute_masking covers 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_rule
• dynatrace_host_monitoring

Bug Fixes

• #356 - Attribute has_http_error not handled properly for resource calculated_mobile_metric
• #360 - dynatrace_auto_tag_v2 created plans with empty rules
• #359 - dynatrace_azure_service clashed with default services Dynatrace assumes when creating dynatrace_azure_credentials. The resource dynatrace_azure_credentials now offers an attribute remove_defaults signalling that any Azure Services Dynatrace creates by default will get removed upon creation.
• Updating dynatrace_network_zone could potentiall crash the provider because of nil point access

v1.46.1

v1.46.1 fixes #344 and #333 - both related to the resource dynatrace_json_dashboard

v1.46.0

New Resources

• dynatrace_url_based_sampling covers configuration for URL-based sampling

Updated Resources

The following resources have been updated to support the most recent schema version offered by the Dynatrace API

• dynatrace_alerting
• dynatrace_os_services

Bug Fixes

• #346 - Fixed dynatrace_generic_setting update
• #349 - Resolved dynatrace_slo_v2 whitespace issue
• #350 - Corrected typo in dynatrace_azure_supported_services documentation
• #351 - Fixed behavior of environment variables for IAM resources

v1.45.0

New Resources

• dynatrace_key_user_action covers management of Key User Actions for Web Applications. Key User Actions until now could only get managed as part of the resource dynatrace_web_application. That functionality is now deprecated - although still possible.

Bug Fixes

• #343 - The property entities of data source dynatrace_entities got evaluated by Terraform as empty list prematurely
• Applying dynatrace_dashboard_sharing was broken since 1.43.0

v1.44.1

Updated Resources

The following resources have been updated to support the most recent schema version offered by the Dynatrace API

• dynatrace_os_services

Improvements

• Updated dynatrace_network_zone to generate name field for export utility

Bug Fixes

• #338 - dynatrace_entity and dynatrace_entities data sources updated with from and to attributes
• #339 - dynatrace_application_detection_rule resource updated to retry when REST API responds with error