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

on GitHub

New Resources

• dynatrace_pg_alerting introduces configuration for process group availability monitoring
• dynatrace_custom_tags introduces configuration for custom/manual tags

New Data Sources

• dynatrace_entity allows querying a specific entity by its name and type
• dynatrace_entities allows querying all entities by its type

Additional Improvements

• The full source code of this project is now contained within one repository.

• Certain resources required -parallelism=1 to be specified for terraform apply. This is not necessary anymore.

• The resource dynatrace_alerting, dynatrace_management_zone_v2, dynatrace_maintenance now offer a computed attributed legacy_id. These resources are using the new Settings 2.0 API Endpoint - which unfortunately produces IDs that cannot directly be used within settings based on the Configuration API. When e.g. configuring a resource dynatrace_notification (based on Configuration API) and want to refer to an Alerting Profile configured via dynatrace_alerting (Settings 2.0), you can now refer to the Alerting Profile using dynatrace_alerting.<resourcename>.legacy_id.

• Resources containing multi-line strings are now able to safely use Heredoc syntax without terraform plan acting up.

• terraform-provider-dynatrace -export downloads resources now in parallel

• terraform-provider-dynatrace -export generates direct references to resources instead of using data sources

• #176: dynatrace_aws_credentials now allows for managing Supported Services via WebUI only (Terraform ignores them)

• Improved dynatrace_http_monitor

  • Support for adapting request timeout
  • Client certificates
  • Request and Response Body aswell as Header Values are not getting stored during execution

Bug Fixes

• Fixed dynatrace_autotag, dynatrace_management_zone, dynatrace_mangement_zone_v2 where the order of rules led to non empty plans
• Fixed dynatrace_request_attribute is now able to handle the enabled property