dynatrace-oss/terraform-provider-dynatrace v1.22.0

on GitHub

New Resources

• dynatrace_browser_monitor_outage introduces configuration for browser monitor outage handling (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)
• dynatrace_http_monitor_outage introduces configuration for HTTP monitor outage handling (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)
• dynatrace_cloudapp_workloaddetection merges processes of similar workloads into process groups, and consequently, services. Please note that fine-grained process detection rules will still be applied, while ignoring container or platform specific properties
• dynatrace_mainframe_transaction_monitoring covers additional monitoring settings for CICS and IMS transactions
• dynatrace_monitored_technologies_apache covers configuration to enable/disable Apache HTTP Server monitoring
• dynatrace_monitored_technologies_dotnet covers configuration to enable/disable .NET monitoring
• dynatrace_monitored_technologies_go covers configuration to enable/disable Golang monitoring
• dynatrace_monitored_technologies_iis covers configuration to enable/disable IIS monitoring
• dynatrace_monitored_technologies_java covers configuration to enable/disable Java monitoring
• dynatrace_monitored_technologies_nginx covers configuration to enable/disable Nginx monitoring
• dynatrace_monitored_technologies_nodejs covers configuration to enable/disable NodeJS monitoring
• dynatrace_monitored_technologies_opentracing covers configuration to enable/disable OpenTracing monitoring
• dynatrace_monitored_technologies_php covers configuration to enable/disable PHP monitoring
• dynatrace_monitored_technologies_varnish covers configuration to enable/disable Varnish monitoring
• dynatrace_monitored_technologies_wsmb covers configuration to enable/disable IBM Integration Bus | IBM App Connect Enterprise monitoring
• dynatrace_process_visibility covers configuration for process instance snapshots
• dynatrace_rum_host_headers covers configuration for identifying host names for real user monitoring
• dynatrace_rum_ip_determination covers configuration for identifying client IP addresses for real user monitoring
• dynatrace_mobile_app_request_errors covers configuration for mobile application request errors
• dynatrace_transaction_start_filters covers customization of CICS and IMS Monitoring
• dynatrace_oneagent_features allows for enabling and disabling OneAgent Features (Sensors, ...)
• dynatrace_rum_overload_prevention covers configuration for real user monitoring overload prevention
• dynatrace_rum_advanced_correlation covers configuration for real user monitoring advanced correlation
• dynatrace_web_app_beacon_origins covers configuration for web application beacon origin allowlist
• dynatrace_web_app_resource_types covers configuration for web application resource types
• dynatrace_generic_types covers configuration for custom topology generic types
• dynatrace_generic_relationships covers configuration for custom topology relationships

Improvements

• Attempting to delete a resource the REST API considers non-deletable doesn't lead to an error anymore
• #168 - Properties shared and sharing_details for resource dynatrace_dashboard are now deprecated (in favor of dynatrace_dashboard_sharing)
• #105 - Changing the metric key of calculated_service_metric now automatically re-creates the resource
• #89 - dynatrace_dashboard_sharing retries to create the resource in case the cluster is not yet fully aware of the existence of the dashboard referred to
• Clarified API Token requirements for resource dynatrace_credentials. Thanks to @paulmorar for contributing
• The data sources dynatrace_management_zone and dynatrace_alerting_profile now offer the attribute legacy_id so they can get referred to from resources with non Settings 2.0 scope
• Introduced the environment variables DYNATRACE_SOURCE_ENV_URL and DYNATRACE_SOURCE_API_TOKEN for the export functionality. The environment variables DYNATRACE_ENV_URL and DYNATRACE_API_TOKEN are still supported, but the new variable names are being preferred. This is meant to prevent unintentionally pushing resources that have just been exported into the same environment again.
• Introduced the option -datasources for the export functionality. When specified, dependencies of resources to dynatrace_management_zone, dynatrace_management_zone_v2,dynatrace_alerting_profile, dynatrace_alerting, dynatrace_request_attribute and dynatrace_web_application will generate data sources instead of exporting these resources.

Bug Fixes

• Fixed #198 - Unable to modify the custom application configuration due to "IconType"
• Fixed #202 - non empty plans for dynatrace_json_dashboard with external JSON source
• Fixed #204 - Incorrect Bearer Token and Credential handling for resources dynatrace_iam_user and dynatrace_iam_group
• Fixed #207 - White Space changes in Entity Selectors of dynatrace_management_zone may lead to non empty plan
• The attributes of Data Sources generated by the export functionality are now getting properly escaped