v1.54.2

Bug Fixes

• #429 - dynatrace_mobile_application - fixed opt_in_mode to properly send when set to false for mobile applications

Improvements

Introduced insert_after attribute for the following Settings 2.0 resources with ordering support:

• dynatrace_api_detection
• dynatrace_application_detection_rule_v2
• dynatrace_attack_allowlist
• dynatrace_attack_rules
• dynatrace_business_events_buckets
• dynatrace_business_events_oneagent
• dynatrace_business_events_processing
• dynatrace_business_events_security_context
• dynatrace_container_rule
• dynatrace_declarative_grouping
• dynatrace_failure_detection_rules
• dynatrace_generic_types
• dynatrace_grail_security_context
• dynatrace_issue_tracking
• dynatrace_log_buckets
• dynatrace_log_processing
• dynatrace_log_security_context
• dynatrace_log_sensitive_data_masking
• dynatrace_log_storage
• dynatrace_log_timestamp
• dynatrace_os_services
• dynatrace_process_availability
• dynatrace_process_group_detection
• dynatrace_process_group_simple_detection
• dynatrace_process_monitoring_rule
• dynatrace_rum_host_headers
• dynatrace_rum_ip_determination
• dynatrace_rum_provider_breakdown
• dynatrace_service_external_web_request
• dynatrace_service_external_web_service
• dynatrace_service_full_web_request
• dynatrace_service_full_web_service
• dynatrace_span_capture_rule
• dynatrace_span_context_propagation
• dynatrace_span_entry_point
• dynatrace_url_based_sampling
• dynatrace_vulnerability_code
• dynatrace_vulnerability_third_party
• dynatrace_web_app_resource_cleanup
• dynatrace_web_app_resource_types

Schema Updates

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

• dynatrace_attack_rules
• dynatrace_custom_service
• dynatrace_generic_relationships
• dynatrace_generic_types
• dynatrace_log_storage
• dynatrace_request_attribute
• dynatrace_vulnerability_settings

v1.54.1

Important Changes (Repeat - Reminder)

The following resources can result in non-empty plans due to a recent update in the REST API. Starting with v287, the API will return the Settings 2.0 ID of any referenced Management Zone ID of the schemas below instead of the configuration V1 ID that it previously returned. In order to resolve this issue, please update any Management Zone references from legacy_id to id. Any hardcoded Management Zone will need to be updated to the Settings 2.0 ID equivalent to result in a non-empty plan.

• builtin:alerting.profile
• builtin:appsec.notification-alerting-profile
• builtin:failure-detection.environment.rules
• builtin:service-detection.external-web-request
• builtin:service-detection.external-web-service
• builtin:service-detection.full-web-request
• builtin:service-detection.full-web-service

Bug Fixes

• #426 - Running the export functionality with an invalid API Token can crash the utility
• #427 - Unnecessary additional HTTP traffic (required for resources supporting the attribute insert_after) for almost all resources

Improvements

• Introduced the environment variable DT_BACKWARDS_COMPATIBILITY. A set of attributes and resource blocks will be treated as optional in this case, even when they are normally flagged as required. Use case: Migrating Settings from very outdated Dynatrace Clusters to new Environments.

v1.54.0

Important Changes (Repeat - Reminder)

The following resources can result in non-empty plans due to a recent update in the REST API. Starting with v287, the API will return the Settings 2.0 ID of any referenced Management Zone ID of the schemas below instead of the configuration V1 ID that it previously returned. In order to resolve this issue, please update any Management Zone references from legacy_id to id. Any hardcoded Management Zone will need to be updated to the Settings 2.0 ID equivalent to result in a non-empty plan.

• builtin:alerting.profile
• builtin:appsec.notification-alerting-profile
• builtin:failure-detection.environment.rules
• builtin:service-detection.external-web-request
• builtin:service-detection.external-web-service
• builtin:service-detection.full-web-request
• builtin:service-detection.full-web-service

New Resources

• dynatrace_db_app_feature_flags covers configuration for database app feature flags (only to be used with direction by Dynatrace ONE)
• dynatrace_infraops_app_feature_flags covers configuration for infrastructure and operations app feature flags (only to be used with direction by Dynatrace ONE)

Improvements

• #412 - All Settings 2.0 resources will now be passing a repairInput query parameter to allow lenient validation. This is an enhancement for maintaining schemas and backwards compatibility for older clusters.

Schema Updates

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

• dynatrace_web_app_javascript_updates
• dynatrace_url_based_sampling

v1.53.0

Important Changes (Repeat - Reminder)

The following resources can result in non-empty plans due to a recent update in the REST API. Starting with v287, the API will return the Settings 2.0 ID of any referenced Management Zone ID of the schemas below instead of the configuration V1 ID that it previously returned. In order to resolve this issue, please update any Management Zone references from legacy_id to id. Any hardcoded Management Zone will need to be updated to the Settings 2.0 ID equivalent to result in a non-empty plan.

• builtin:alerting.profile
• builtin:appsec.notification-alerting-profile
• builtin:failure-detection.environment.rules
• builtin:service-detection.external-web-request
• builtin:service-detection.external-web-service
• builtin:service-detection.full-web-request
• builtin:service-detection.full-web-service

New Resources

• dynatrace_hub_extension_config and dynatrace_hub_extension_active_version cover configuration Extensions that are eligible to get installed via Dynatrace Hub.

New Data Sources

• dynatrace_hub_items covers querying for components that are available on the Dynatrace Hub, like Extensions or Technologies

Bug Fixes

#418 - Deleting dynatrace_environment resource instances was not always possible in combination with licensing constraints
#421 - Resource dynatrace_ownership_teams insisted on specifying a url within the contact_details when the integration_type was either SLACK. That attribute is however optional in such a case

Improvements

• dynatrace_log_processing now offers the attribute insert_after - which allows for defining the order of multiple resource instances of type dynatrace_log_processing

v1.52.0

Important Changes

The following resources can result in non-empty plans due to a recent update in the REST API. Starting with v287, the API will return the Settings 2.0 ID of any referenced Management Zone ID of the schemas below instead of the configuration V1 ID that it previously returned. In order to resolve this issue, please update any Management Zone references from legacy_id to id. Any hardcoded Management Zone will need to be updated to the Settings 2.0 ID equivalent to result in a non-empty plan.

• builtin:alerting.profile
• builtin:appsec.notification-alerting-profile
• builtin:failure-detection.environment.rules
• builtin:service-detection.external-web-request
• builtin:service-detection.external-web-service
• builtin:service-detection.full-web-request
• builtin:service-detection.full-web-service

New Resources

• dynatrace_managed_network_zones covers configuration for Managed cluster network zones

New Data Sources

• dynatrace_management_zone_v2 covers queries for the ID of a management zone based on name. This new v2 data source will only require the settings.read scope since it is using the Settings 2.0 API. This will be used as the default for Management Zone dependencies in the export utility.

Improvements

• Introduced export capability for dynatrace_policy_bindings and dynatrace_mgmz_permission

Schema Updates

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

• dynatrace_business_events_oneagent
• dynatrace_calculated_service_metric
• dynatrace_credentials
• dynatrace_request_attribute
• dynatrace_web_application

v1.51.0

New Resources

• dynatrace_http_monitor_script introduces the ability to maintain HTTP Requests outside of resource dynatrace_http_monitor.

Bug Fixes

• #407 - dynatrace_webhook_notification with secret_url ended up with non-empty plans
• The attribute urls of resource dynatrace_dashboard_sharing wasn't flagged as Optional

Improvements

• Introduced export capability for dynatrace_user_group
• Introduced export capability for dynatrace_user
• The new optional attribute mode for resource dynatrace_opentelemetry_metrics now allows for multiple resource instances to maintain independent subsets of attributes.

v1.50.0

New Resources

• dynatrace_iam_policy_bindings_v2 covers binding policies to user groups via Account Management API for SaaS Accounts. This resource works similar to dynatrace_iam_policy_bindings, but also allows for specifying parameters and metadata to the bindings.
• dynatrace_kubernetes_app covers configuration to enable the new Kubernetes app.
• dynatrace_grail_metrics_allowall covers configuration to allow all custom metric ingestion to Grail.
• dynatrace_grail_metrics_allowlist covers allow list configuration of custom metric ingestion to Grail.
• dynatrace_web_app_beacon_endpoint covers configuration for web application beacon endpoint.
• dynatrace_web_app_custom_config_properties covers configuration for web application custom configuration properties.
• dynatrace_web_app_injection_cookie covers configuration for web application cookies.

Bug Fixes

• #398 - Updated dynatrace_aws_service resource dimensions field to an ordered list. Pending R&D fix, dimensions will be switched back to an unordered list.

Improvements

• Introduced export capability for dynatrace_policy

Schema Updates

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

• dynatrace_iam_group
• dynatrace_iam_permission
• dynatrace_process_availability

v1.49.2

Bug Fixes

• #394 - Resolved dynatrace_management_zone_v2 issue where case_sensitive false was being driven to null with AZURE_ENTITY_NAME condition.
• #395 - Resolved dynatrace_calculated_service_metric issue where the UniversalTag was not being properly unmarshalled.
• #397 - Resolved dynatrace_aws_credentials issue where supported services were being deleted and tags_to_monitor were being shuffled.

Schema Updates

The following resource was updated to be compatible with the most recent schema version of Dynatrace:

• dynatrace_disk_options

v1.49.1

• Fixed missing documentation from v1.49.0

v1.49.0

New Resources

• dynatrace_attribute_block_list covers configuration for OpenTracing and OpenTelemetry attribute block-list
• dynatrace_attributes_preferences covers configuration for OpenTracing and OpenTelemetry attribute preferences
• dynatrace_crashdump_analytics covers configuration for crash dump analytics
• dynatrace_app_monitoring covers configuration for Dynatrace app monitoring
• dynatrace_grail_security_context covers configuration for Grail security context
• dynatrace_site_reliability_guardian covers configuration for Site Reliability Guardian
• dynatrace_automation_workflow_jira covers configuration for Jira for Workflows
• dynatrace_automation_workflow_slack covers configuration for Slack for Workflows

Bug Fixes

• #386 - Terrafrom Provider for AWS treats an optional entityFilter block as required and errors out
• Applying an entity_selector for resource dynatrace_management_zone_v2 in heredoc syntax led to non-empty plans
• Applying dynatrace_service_anomalies_v2 without a scope leads to provider crash

Updated Schemas for existing resources

• dynatrace_os_services
• dynatrace_host_monitoring_advanced