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

dynatrace_web_app_request_errors covers configuration for web application request errors
dynatrace_user_settings covers user settings of an individual user
dynatrace_dashboards_general covers configuration for general dashboard settings
dynatrace_dashboards_presets covers configuration for dashboard preset settings
dynatrace_iam_policy covers policy configuration via Account Management API for SaaS Accounts
dynatrace_iam_policy_bindings covers binding policies to user groups via Account Management API for
dynatrace_policy covers policy configuration via Account Management API for Managed Clusters
dynatrace_policy_bindings covers binding policies to user groups via Account Management API for Managed Clusters
dynatrace_log_processing covers configuration for log processing
dynatrace_log_events covers configuration for log events
dynatrace_log_timestamp covers configuration for log timestamp
dynatrace_log_grail covers configuration for log powered by Grail
dynatrace_eula_settings covers configuration for display of the clickwrap agreement
dynatrace_api_detection covers configuration for API detection rules
dynatrace_service_external_web_request covers service detection rules for external web requests

Fixed #209 - Password field for dynatrace_credentials couldn't get omitted
Fixed #218 - metadata block for dynatrace_metric_events ignored on apply
Fixed #220 - Resource dynatrace_aws_credentials did not reliably produce empty plans
Fixed: Specifying invalid values (not accepted by the REST API) for certain attributes in resources dynatrace_*_notification may lead to plugin crash
Fixed: Environment variable mismatch when using terraform-provider-dynatrace -export -import-state
Fixed: URL for fetching dynatrace_slo was not properly escaped. Thanks to @csy2018 for contributing that fix!

dynatrace_alerting now supports metadata within custom filters
We've noticed that the Dynatrace REST API for several resources may reject the configuration when certain boolean attributes are not being sent - even if they are optional and even if they default to false. However, the changes we've introduced to cope with that situation don't change the behavior of the resources at all. We just wanted to have them noted down within the release notes.