v1.29.0

New Resources

• dynatrace_kubernetes covers the Settings 2.0 schema for Kubernetes/OpenShift monitoring. You can still continue to use dynatrace_kubernetes_credentials, but that resource doesn't cover all possible attributes. dynatrace_kubernetes covers all of them
• dynatrace_cloud_foundry covers configuration for Cloud Foundry monitoring
• dynatrace_disk_anomaly_rules covers configuration for disk anomaly detection rules
• dynatrace_aws_anomalies covers configuration for AWS anomaly detection
• dynatrace_vmware_anomalies covers configuration for AWS anomaly detection
• dynatrace_slo_v2 covers configuration for service-level objectives
• dynatrace_autotag_v2 covers configuration for automatically applied tags
• dynatrace_slo_v2 covers configuration for service-level objectives
• dynatrace_log_buckets covers configuration for log buckets
• dynatrace_business_events_oneagent covers configuration for OneAgent business events
• dynatrace_business_events_buckets covers configuration for business event bucket assignment
• dynatrace_business_events_metrics covers configuration for business event metric extraction
• dynatrace_business_events_processing covers configuration for business event processing

Bug Fixes

• Attribute dashboard_metadata.tiles_name_size in resource dynatrace_dashboard was wrongfully modelled as int instead of string
• #237 - Preventing potential panic within the provider when updating dynatrace_slo resources
• #231 - The attribute follow_redirects in resource dynatrace_http_monitor couldn't get updated anymore
• dynatrace_session_replay_web_privacy: url_exclusion_pattern_list is now optional
• dynatrace_session_replace_capture: resource_capture_url_exclusion_pattern_list is now optional
• dynatrace_generic_types: required_dimensions, role and attributes are now optional
• dynatrace_disk_options: exclusions is now optional
• dynatrace_dashboards_presets: dashboard_presets_list is now optional
• dynatrace_api_detection: conditions is now optional
• dynatrace_declarative_grouping: rules is now optional
• dynatrace_queue_manager: clusters now correctly synchronized with backend
• dynatrace_log_events: metadata is now optional
• dynatrace_log_metrics: dimensions is now optional
• dynatrace_log_timestamp: matchers is now optional
• dynatrace_metric_metadata: dimensions and tags is now optional
• dynatrace_email_notification: cc and bcc now correctly with backend
• dynatrace_process_availability: metadata and rules now correctly with backend
• dynatrace_cloudapp_workloaddetection: filters is now optional
• dynatrace_resource_attributes: keys now correctly synchronized with backend
• dynatrace_mobile_app_request_errors: error_rules is now optional
• dynatrace_web_app_custom_errors: error_rules is now optional
• dynatrace_web_app_request_errors: error_rules is now optional
• dynatrace_muted_requests: muted_request_names is now optional
• dynatrace_key_requests: names now correctly synchronized with backend
• dynatrace_browser_monitor_performance: thresholds is now optional
• dynatrace_http_monitor_performance: thresholds is now optional
• dynatrace_http_monitor_performance: thresholds is now optional
• dynatrace_metric_events: legacy_id is now properly getting generated and is now a computed attribute
• #241 - corrected report enum for dynatrace_declarative_grouping schema
• dynatrace_host_anomalies_v2: high_system_load_detection is now a required block
• #238 - dynatrace_dashboard_sharing now offers anonymous access URLs as computed attribute
• #235 - In case IAM resources receive a 504 (Gateway Timeout) the provider attempts several retries

Additional Improvements

• Updated dynatrace_monitored_technologies_php schema to v0.0.3
• Updated dynatrace_transaction_start_filters schema to v1.2
• Resources dynatrace_process_group_detection and dynatrace_generic_relationships are able to detect duplicates during terraform apply
• The export functionality now merges dynatrace_json_dashboard and dynatrace_dashboard_sharing into the same .tf files
• Utilizing Data Sources now produces debug log output
• Improved error messages for several resources where combinations of certain attributes are not allowed
• Several resources with attributes like metric_selector where it looks more user friendly to use Heredoc Syntax won't produce a non-empty plan anymore