Skip to content

Releases: dynatrace-oss/terraform-provider-dynatrace

v1.30.0

10 May 09:17

Choose a tag to compare

New Resources

Bug Fixes

  • #244 - Plugin potentially crashes when using data source dynatrace_alerting_profiles

Additional Improvements

  • The export functionality now exports dynatrace_dashboard_sharing at the end of dynatrace_json_dashboard
  • The export functionality now exports several dependent resources at the end of dynatrace_web_application
  • The export functionality now exports several dependent resources at the end of dynatrace_web_application

v1.29.0

05 May 13:42

Choose a tag to compare

New Resources

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

v1.28.0

21 Apr 13:23

Choose a tag to compare

New Resources

New Data Sources

  • dynatrace_dashboard allows you to query for a dashboard based on name and owner
  • dynatrace_slo allows you to query for a SLO based on name
  • dynatrace_mobile_application allows you to query for a mobile application based on name

Bug Fixes

  • Fixed #228 - Fixed dynatrace_request_attribute to retrieve the proper ID
  • Fixed #229 - Updated dynatrace_web_application key_user_actions as an unordered list
  • Fixed #230 - Added special handling for dynatrace_request_attribute argument_types field
  • Fixed #236 - Added possible values in dynatrace_management_zone_v2 documentation
  • Corrected dynatrace_disk_specific_anomalies_v2 fields disk_low_inodes_detection, disk_low_space_detection, and disk_slow_writes_and_reads_detection as optional
  • Corrected dynatrace_pg_alerting field alerting_mode as optional

Additional Improvements

  • Updated dynatrace_monitored_technologies_php schema to v0.0.3
  • Updated dynatrace_k8s_node_anomalies schema to v1.2.2
  • Updated dynatrace_k8s_workload_anomalies schema to v1.7

v1.27.0

12 Apr 10:17

Choose a tag to compare

New Resources

New Data Sources

  • dynatrace_request_naming allows you to query for request naming settings based on name

Bug Fixes

  • Fixed #225 - Updates for dynatrace_custom_tag deleted the wrong objects.
  • Fixed #225 - Increased the polling timeout after applying dynatrace_web_application. The provider now tries up to 60 seconds by default to validate whether the Web Application is known cluster wide.
  • Fixed #226 - The results of terraform-provider-dynatrace -export created non-immutable results because of auto-generated IDs for resource names

Improvements

  • The environment variable DYNATRACE_CREATE_CONFIRM_WEB_APPLICATION allows you to increase the polling timeout for validating whether a freshly applied dynatrace_web_application is known cluster wide. Defaults to 60.

v1.26.0

05 Apr 13:08

Choose a tag to compare

New Resources

Bug Fixes

  • Fixed #224 - The JSON property 'popularity' leads to non-empty plans for resources dynatrace_json_dashboard

Improvements

  • Introduced generic_tag_filters for resource dynatrace_dashboard
  • The attribute supporting_services_managed_in_dynatrace for resource dynatrace_aws_credentials enables users to manage supported services via WebUI only - Terraform won't interfere

v1.25.1

28 Mar 09:45

Choose a tag to compare

Fixed ##221

v1.25.0

27 Mar 14:06

Choose a tag to compare

New Resources

  • 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

Bug Fixes

  • 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!

Improvements

  • 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.

v1.24.0

21 Mar 09:25

Choose a tag to compare

New Resources

  • dynatrace_activegate_token introduces configuration for ActiveGate network security
  • dynatrace_audit_log introduces configuration for audit log
  • dynatrace_mgmz_permission introduces permissions to user groups / management zones within managed environments
  • dynatrace_k8s_cluster_anomalies introduces configuration for Kubernetes cluster anomalies
  • dynatrace_k8s_namespace_anomalies introduces configuration for Kubernetes namespace anomalies
  • dynatrace_k8s_node_anomalies introduces configuration for Kubernetes node anomalies
  • dynatrace_k8s_workload_anomalies introduces configuration for Kubernetes workload anomalies
  • dynatrace_container_builtin_rule introduces configuration for builtin monitoring rules for containers
  • dynatrace_container_rule introduces configuration for monitoring rules for containers
  • dynatrace_container_technology introduces configuration for container monitoring
  • dynatrace_remote_environments introduces configuration for remote Dynatrace environments
  • dynatrace_web_app_custom_errors introduces configuration for web application custom errors

Bug Fixes

  • Fixed #216 - Resolved dynatrace_iam_group update to PUT instead of POST

v1.23.0

15 Mar 14:11

Choose a tag to compare

New Resources

  • dynatrace_slo_normalization introduces configuration for service-level objective setup
  • dynatrace_data_privacy introduces configuration for end users' data privacy OVERLAP
  • dynatrace_service_failure introduces configuration for service-level general failure detection parameters
  • dynatrace_service_http_failure introduces configuration for service-level HTTP failure detection parameters
  • dynatrace_disk_options introduces configuration for host disk visibility settings
  • dynatrace_os_services introduces configuration for monitoring OS services
  • dynatrace_extension_execution_controller introduces Extension Execution Controller configuration for OneAgent deployment
  • dynatrace_nettracer introduces configuration for NetTracer traffic
  • dynatrace_aix_extension introduces configuration for AIX kernel extension
  • dynatrace_metric_metadata introduces configuration for metric metadata
  • dynatrace_metric_query introduces configuration for metric query
  • dynatrace_iam_permission introduces configuration for user permissions via Account MAnagement API for SaaS accounts

New Data Source

  • dynatrace_iam_user fetches the groups the user identified with the given email

Bug Fixes

  • Fixed #213 - Modified unknowns field in dynatrace_dashboard to suppress diff on isAutoRefreshDisabled

v1.22.2

10 Mar 15:33

Choose a tag to compare

  • Fix: dynatrace_request_attribute didn't properly query for the scope process group ID
  • Export Functionality
    • Fix: __datasources__.tf files were missing new lines in certain cases
    • Fix: Data Sources for Management Zones used dynatrace_management_zone_v2 instead of dynatrace_management_zone
    • Improvement: Resources are now not anymore moved to the .flawed folder, but are symbolic links