v1.35.2

We apologize for two flawed releases in a row. Releases v1.35.0 and v1.35.1 got pushed out too hastily.
Again, here are the release notes for v1.35.x.

New Resources

• dynatrace_custom_device covers the configuration of Custom Devices. Thanks @vlad-preutu for contributing the source code!
• dynatrace_k8s_monitoring covers the configuration for Kubernetes monitoring settings

Improvements

• The documentation of dynatrace_aws_service contained invalid examples. Thanks @agentreno for fixing that!
• The documentation in the Terraform Registry now contains an up-to-date list of permissions for the API Tokens
• The documentation of resources utilizing deprecated REST APIs of Dynatrace (e.g. dynatrace_management_zone) now contains a note at the very beginning, recommending a different resource.
• String attributes of all resources are now less likely to produce a non-empty plan when heredoc syntax is being used

Bug Fixes

• #295 - The provider complained about the missing provider properties dt_env_url and dt_api_token even if non of the configured resources or data sources depended on them (e.g. dynatrace_iam_user)

Updated Resources

The following resources have been updated to support the most recent Schema Version offered by the Dynatrace API - supporting the most recent set of attributes and their documentation offered by the API

• dynatrace_vmware
• dynatrace_extension_execution_controller
• dynatrace_log_grail
• dynatrace_alerting
• dynatrace_webhook_notification
• dynatrace_management_zone_v2
• dynatrace_webhook_notification
• dynatrace_kubernetes
• dynatrace_log_oneagent

v1.35.1

This is just a hotfix release for v1.35.0. The provider itself didn't change, but small changes to the export functionality:

• Removed unnecessary debug output
• The command line flags -import-state and -import-state-v2 didn't get evaluated properly

v1.35.0

New Resources

• dynatrace_custom_device covers the configuration of Custom Devices. Thanks @vlad-preutu for contributing the source code!

Improvements

• The documentation of dynatrace_aws_service contained invalid examples. Thanks @agentreno for fixing that!
• The documentation in the Terraform Registry now contains an up-to-date list of permissions for the API Tokens
• The documentation of resources utilizing deprecated REST APIs of Dynatrace (e.g. dynatrace_management_zone) now contains a note at the very beginning, recommending a different resource.
• String attributes of all resources are now less likely to produce a non-empty plan when heredoc syntax is being used

Bug Fixes

• #295 - The provider complained about the missing provider properties dt_env_url and dt_api_token even if non of the configured resources or data sources depended on them (e.g. dynatrace_iam_user)

Updated Resources

The following resources have been updated to support the most recent Schema Version offered by the Dynatrace API - supporting the most recent set of attributes and their documentation offered by the API

• dynatrace_vmware
• dynatrace_extension_execution_controller
• dynatrace_log_grail
• dynatrace_alerting
• dynatrace_webhook_notification
• dynatrace_management_zone_v2
• dynatrace_webhook_notification
• dynatrace_kubernetes
• dynatrace_k8s_monitoring
• dynatrace_log_oneagent

v1.34.0

New Resources

• dynatrace_limit_outbound_connections covers configuration for limiting outbound connections running in the Dynatrace JavaScript runtime.
• dynatrace_span_events covers configuration for span events.
• dynatrace_vmware covers configuration for VMware.
• dynatrace_web_app_key_performance_custom covers configuration for apdex threshold configuration for custom actions.
• dynatrace_web_app_key_performance_load covers configuration for apdex threshold configuration for load actions.
• dynatrace_web_app_key_performance_xhr covers configuration for apdex threshold configuration for XHR actions.

New Data Sources

• dynatrace_synthetic_nodes covers queries for synthetic nodes.
• dynatrace_tenant is a pseudo data source, it evaluates based on the configuration of the provider environment ID.

Improvements

• The export utility now allows resources dynatrace_iam_user and dynatrace_iam_group export with dependencies.

Bug Fixes

• #276 - dynatrace_entity data source produced an ID even if no entity matched the given name
• #278 - dynatrace_synthetic_location resource of type Kubernetes asked for non-existent attributes
• #279 - dynatrace_browser_monitor resource field key_performance_metrics was incorrectly marked as optional
• #280 - Improved error checking to validate the environment URL and API token are set
• #282 - dynatrace_web_application resource could produce non-empty plans

v1.33.0

New Resources

• dynatrace_builtin_process_monitoring covers configuration for built-in process monitoring rules.

New Data Sources

• Data Source dynatrace_azure_credentials covers queries for Azure credentials.
• Data Source dynatrace_aws_credentials covers queries for AWS credentials.
• Data Source dynatrace_update_windows covers queries for maintenance windows for OneAgent updates.
• Data Source dynatrace_failure_detection_parameters covers queries for failure detection parameters.

Improvements

• Data Sources dynatrace_entity and dynatrace_entities are now offering properties for the queried entities

Bug Fixes

• dynatrace_dashboard_sharing can now safely get used for Dashboards that are flagged as preset
• The export functionality now continues postprocessing even when network / server side errors occur
• Using the switch -datasources with the export functionality didn't clean up temporary resource folders
• #273 - dynatrace_application_detection_rule produced non empty plans when attribute name was not specified

Updated Resources

The following resources have been updated to support the most recent Schema Version offered by the Dynatrace API - supporting the most recent set of attributes and their documentation offered by the API

• dynatrace_data_privacy
• dynatrace_generic_types
• dynatrace_host_monitoring
• dynatrace_log_buckets
• dynatrace_log_custom_source
• dynatrace_log_processing
• dynatrace_metric_events
• dynatrace_metric_metadata
• dynatrace_opentelemetry_metrics
• dynatrace_ownership_config
• dynatrace_ownership_teams
• dynatrace_service_external_web_request
• dynatrace_data_privacy
• dynatrace_generic_types
• dynatrace_service_external_web_service
• dynatrace_service_full_web_request
• dynatrace_service_full_web_service
• dynatrace_usability_analytics
• dynatrace_service_anomalies_v2
• dynatrace_resource_attributes
• dynatrace_span_attribute
• dynatrace_queue_sharing_groups
• dynatrace_maintenance
• dynatrace_management_zone_v2
• dynatrace_servicenow_notification

v1.32.1

• Updated dynatrace_k8s_workload_anomalies schema to v1.8
• Updated dynatrace_container_technology schema to v1.0.7

v1.32.0

New Resources and Data Sources

• Resource dynatrace_aws_service covers configuration of Supported Services for AWS Credentials.
• Data Source dynatrace_aws_supported_services allows you to query for all supported services configurable fro AWS Credentials.

Bug Fixes

• #267 - The schema for meta_data blocks of resource dynatrace_metric_events got accidentally changed with the previous release.
• #261 - The token value of resource dynatrace_api_token was getting cleared within the Terraform State during subsequent executions of terraform apply

Documentation Improvements

• The documentation for resources that are meanwhile considered deprecated by Dynatrace now refers to the resource that should be used instead (e.g. dynatrace_alerting_profile is deprecated, therefore dynatrace_alerting should be used). Be aware that we will flag these resources as deprecated on Terraform Schema Level in one of the upcoming releases. They may still be used, but the Dynatrace API Endpoints they are using are likely not fully covering all possible configuration options.
• For several resources certain fields have overlap with other resources (e.g. dynatrace_application_error_rules is partially covered by either dynatrace_web_app_request_errors or dynatrace_web_app_custom_errors). The documentation of these resources contains a hint about that fact in order to prevent users from configuring contradictory/inconsistent settings.
• The documentation contains a note for resources that are excluded by default by the export functionality.
• #269 - The documentation of dynatrace_autotag_v2 now contains a sample for how to use the metric_selector attribute
• #270 - Added clarifying comments for the attributes dynamic_key and dynamic_key_source of resource dynatrace_management_zone_v2

v1.31.0

New Resources and Data Sources

• Resource dynatrace_azure_service covers configuration of Supported Services for Azure Credentials. actions](https://www.dynatrace.com/support/help/platform-modules/digital-experience/web-applications/additional-configuration/configure-apdex-web)
• Data Source dynatrace_azure_supported_services allows you to query for all supported services configurable fro Azure Credentials.

Bug Fixes

• #240 - The resource dynatrace_custom_tag had no effect on entities that were not reachable with the default timeframe of 24h. That timeframe has now been changed to the last 3 years.
• #259 - REST API rejects payload for dynatrace_browser_monitor in certain cases
• #263 - The Data Source dynatrace_entities produced empty results in most cases

Documentation

• Introduced environment migration documentation using the export utility and Terraform

Additional Improvements

• The resource dynatrace_credentials is using now the environment V2 API under the hoods.
• The resource dynatrace_metric_events supports the latest schema version offered by Dynatrace (1.0.3 => 1.0.13)
• The data source dynatrace_entity now allows for specifying the attribute entity_selector
• The data source dynatrace_entities now covers any existing entities of the last 3 years

v1.30.2

Bug Fixes

• #247 - dynatrace_browser_monitor containing key stroke events could not get applied
• #251 - The attribute accept_any_certificate of resource dynatrace_browser_monitor could not get applied
• #246 - The attribute id of user_tags in resource dynatrace_web_application is now getting managed by Terraform in order to allow for conveniently add and remove such tags
• #253 - The export functionality is now able to find the terraform CLI on all Linux distributions
• #240 - The resource dynatrace_custom_tag had no effect on entities that were not reachable with the default timeframe of 24h. That timeframe has now been changed to the last 3 years.
• On Mac workstations and some Linux systems the provider wasn't able to produce debug logs

Additional Improvements

• #249 - The resource dynatrace_slo_v2 now offers the attribute legacy_id
• The export functionality is now merging directly dependent resources (privacy settings, error rules) into the same .tf file as dynatrace_web_application
• The export functionality is now merging directly dependent resources into the same .tf file as dynatrace_mobile_application

v1.30.1

• Disabled the resources below since the API endpoints no longer exist
  • dynatrace_web_app_key_performance_load
  • dynatrace_web_app_key_performance_xhr
  • dynatrace_web_app_key_performance_custom