v1.5.0

Release v1.5.0 introduces support for the resource dynatrace_slo.

The download functionality is now deprecated. You should use terraform-provider-dynatrace export now instead. Using that command line option you are now able to download specific resources. Take a look at the README.md for details.

Release v1.6.0 will contain support for maintaining OpenTelemetry Settings.

v1.4.0

New resources supported by v1.4.0:

• dynatrace_service_naming
• dynatrace_host_naming
• dynatrace_processgroup_naming

Fixes:

• #50: JSON payload for Dashboard Tiles required the property assignedEntities even if none are specified
• #48: The attribute tag_filter in Alerting Profile Rules was wrongfully declared as optional
• #46: Tag Comparisons for Calculated Service Metrics didn't allow for the property values

Release v1.5.0 will contain support for SLOs.

v1.3.0

• Introduced the resource dynatrace_calculated_service_metric.

The next minor release will focus on dynatrace_service_naming. Feel free to make suggestions for which resources should get implemented next by filing an issue here on GitHub.

v1.2.2

Fixed #45: terraform-provider-dynatrace download results in too many open files error when too many resources need to get downloaded
Fixed #43: terraform-provider-dynatrace download overwrites resources with the same name but different unique id. The resulting .tf files now contain the unique ID within their name.
Fixed #42 and #41: The attribute samples when using static monitoring strategy for resource dynatrace_custom_anomalies didn't get serialized properly.
Fixed #40: Certain resources created a terraform state too early within the process, therefore resulting in a flawed state when configured with invalid parameters.
Fixed #39: Instructions for using the provider now refer to source dynatrace-oss/dynatrace instead of dynatrace.com/com/dynatrace.

v1.2.1

Release v1.2.1 includes updated documentation for the supported resources of v1.2.0.

---

Resources introduced with v1.2.0:

• dynatrace_service_anomalies
• dynatrace_application_anomalies
• dynatrace_host_anomalies
• dynatrace_database_anomalies
• dynatrace_custom_anomalies
• dynatrace_disk_anomalies

When importing dynatrace_service_anomalies, dynatrace_application_anomalies, dynatrace_host_anomalies or dynatrace_database_anomalies using terraform import, please be aware of the fact, that they represent permanent configuration - and therefore are not represented by a unique identifier. It's recommended to use the resource identifier instead of the ID, like in this example.

terraform import dynatrace_database_anomalies.dynatrace_database_anomalies dynatrace_database_anomalies

Bug Fixes:

• #35: Resources exported via direct invocation of the provider executable will not contain white spaces anymore
• #36: Applying a faulty configuration for dynatrace_notification resulted in a tainted state being created

v1.2.0

Resources introduced with v1.2.0:

• dynatrace_service_anomalies
• dynatrace_application_anomalies
• dynatrace_host_anomalies
• dynatrace_database_anomalies
• dynatrace_custom_anomalies
• dynatrace_disk_anomalies

When importing dynatrace_service_anomalies, dynatrace_application_anomalies, dynatrace_host_anomalies or dynatrace_database_anomalies using terraform import, please be aware of the fact, that they represent permanent configuration - and therefore are not represented by a unique identifier. It's recommended to use the resource identifier instead of the ID, like in this example.

terraform import dynatrace_database_anomalies.dynatrace_database_anomalies dynatrace_database_anomalies

Bug Fixes:

• #35: Resources exported via direct invocation of the provider executable will not contain white spaces anymore
• #36: Applying a faulty configuration for dynatrace_notification resulted in a tainted state being created

v1.1.1

With the remaining resource dynatrace_notification finally also re-implemented using manual serialization it's now time to reserve revision numbers for bug fixes and increasing the minor version once additional resources are getting introduced.

• It was unfortunately necessary to change the HCL schema for dynatrace_notification. This means you're required to recreate your .tf files for these resources either by re-downloading using terraform-provider-dynatrace download ... or via terraform import.
• The new implementation of dynatrace_notification takes care of #28. The order of the email receivers, cc-receivers and bcc-receivers doesn't matter anymore.
• The resource dynatrace_k8s_credentials now supports the new property davis_events_integration_enabled.
• Fixed #33

v1.1.0

With the remaining resource dynatrace_notification finally also re-implemented using manual serialization it's now time to reserve revision numbers for bug fixes and increasing the minor version once additional resources are getting introduced.

• It was unfortunately necessary to change the HCL schema for dynatrace_notification. This means you're required to recreate your .tf files for these resources either by re-downloading using terraform-provider-dynatrace download ... or via terraform import.
• The new implementation of dynatrace_notification takes care of #28. The order of the email receivers, cc-receivers and bcc-receivers doesn't matter anymore.
• The resource dynatrace_k8s_credentials now supports the new property davis_events_integration_enabled.

v1.0.15

Fixed #32: Condition Keys of type string (string_key) used within dynatrace_management_zone and dynatrace_autotag didn't get translated correctly into JSON, therefore leading to error message from REST API.

v1.0.14

• The resource dynatrace_custom_service has been rewritten. The HCL Schema has remained the same.
• The resource dynatrace_request_attribute has been rewritten in order to support stability in all use cases. The HCL Schema has unfortunately changed. You will have to re-import or re-download the affected .tf files.
• Fixed #30 (attribute case_sensitive didn't get properly persisted) for ip_address comparison for resource dynatrace_management_zone, dynatrace_autotags)