v1.79.2

Bug Fixes

• #676 Corrected dynatrace_network_monitor resource threshold attribute type. Thank you @paulmorar for raising the issue and contributing!
• #678 Fixed dynatrace_oneagent_updates from resulting to a nil pointer dereference

---

Changelog

• 15610d7 v1.79.2
• 15fb0ff Update synthetic monitor type (#677)
• 90c76ef Fixed #678

v1.79.1

Bug Fix

• #675 Using that data source dynatrace_dql without OAuth Credentials crashed the provider. Also the documentation for the resource didn't get produced correctly.
• #670 Added "Use Proxy API for XHRs" toggle to Web Application was not fully resolved.

---

Changelog

• fd9b2e7 Fixed #670
• 3c5c487 Fixed #675

v1.79.0

New Resources and Data Sources

• #674 Introduced data source dynatrace_dql

Bug Fix

• #671 terraform plan for dynatrace_document fails with "unexpected EOF" errors in some environments
• #670 Added "Use Proxy API for XHRs" toggle to Web Application
• #673 Exporting and applying workflows of type SIMPLE leads to errors
• #665 Incorrect order of operations on update of policy boundaries and policy attachment

---

Changelog

• c335a5d v1.79.0
• f812d15 Fixed #665
• becb9aa Merge branch 'main' of https://github.com/dynatrace-oss/terraform-provider-dynatrace
• 4166133 Fixed #674
• 3144151 Updated resource with version update only
• eea3837 Fixed #673
• 0fc92c1 Updated resource with version update only
• abdf9a0 Resolved #670
• b66e4c8 Fixed #671
• dba021d Fixed documentation typo
• 725b4a1 Fixed documentation typos

v1.78.0

New Resources and Data Sources

• The resource dynatrace_platform_slo covers configuration for platform service-level objectives
• The Data Sources dynatrace_platform_slo_templates and dynatrace_platform_slo_template cover queries for the ID of a SLO objective template based on name

Bug Fix

• #664/#666 - Export functionality crashes when cluster credentials are not specified
• #667 - Changing the tags specified within dynatrace_browser_monitor leads to error message

Schema Updates

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

• dynatrace_attack_settings
• dynatrace_vulnerability_settings
• dynatrace_limit_outbound_connections
• dynatrace_request_attribute
• dynatrace_web_application
• dynatrace_synthetic_location

---

Changelog

• 0838348 v1.78.0
• 9ceae96 Introduced platform SLO resource and data sources (#668)
• 1215a9b Fixed #667
• cc3d9fc Fixed #666
• 556c36f Updated dynatrace_vulnerability_settings resource
• ebb85e0 Updated resource with version update only
• 2a1b0fd Updated dynatrace_synthetic_location resource
• 4bcee1b Updated dynatrace_web_application resource
• c11ba64 Updated dynatrace_request_attribute resource
• 7b014c3 Updated resource with version update only
• 342abfa Updated dynatrace_vulnerability_settings resource
• 730a712 Updated dynatrace_attack_settings resource
• fd0059f Reenabled disabled tests due to schema updates
• 5bf70f1 Updated dynatrace_default_launchpad resource

v1.77.0

New Resources

• #501 - Introduced the resources process_group_naming_order, dynatrace_host_naming_order and dynatrace_service_naming_order
• #582 - Introduced the resource dynatrace_custom_service_order

Improvements

• #590 - Added support for authentication via OAuth for all eligible resources. This includes all resources that are based on the Settings 2.0 API. A few remaining resources are still based on endpoints offered by the Config API, simply because there exists no counterpart in Settings 2.0 yet. These resources still require an API Token. Please read this post about how to enforce OAuth credentials for all resources.
• #625 - The documentation for dynatrace_credentials now contains an example for how to upload a certificate file

Bug Fix

• #653 - Updating / deleting dynatrace_slo_v2 resources errored out in certain situations
• #652 - Resource dynatrace_alerting insists on specifying an empty tags attribute in situations where none are allowed to get specified by the REST API
• #642 - Resource dynatrace_http_monitor_script was included in the list of resources exported by default
• The documentation for dynatrace_host_anomalies didn't list the allowed values for on_graceful_shutdowns

Schema Updates

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

• dynatrace_url_based_sampling

---

Changelog

• d9374af v1.77.0
• 930a6b5 Updated dynatrace_url_based_sampling resource
• e9efaee Updated resource with version update only
• ebf0855 Updated supported resources documentation
• f83c622 Updated docs in response of #625
• 80d41d2 fixed typo in doc
• b445c8a Fixed #582
• dac968e updated documentation for attribute on_graceful_shutdowns
• c9ab2c5 Fixed #501
• a774004 streamlined a couple of remaining app-related services to the new rest client structure
• 7b23752 Existing Platform resources streamlined to use the new rest client structure
• db462fe Fixed #642
• 10474fc Introduced Rate Limiter and Retry Options (429 response) for all platform clients
• 00a3e94 Fixed #652
• 6ebb58b Fixed #653
• dc4c716 Bump golang.org/x/net from 0.33.0 to 0.36.0 (#655)
• 0f71ba0 Fixed #590

v1.76.0

New Resource

• A preliminary version of dynatrace_segment covers configuration of segments to logically structure observability data across apps on the Dynatrace platform. Please read the documentation on the Terraform Registry about limitations

Bug Fixes

• #648 Export functionality skips selectOption Synthetic events
• #657 Exporting dynatrace_openpipeline_logs may produce zero results

---

Changelog

• 348e589 v1.76.0
• 5b328ba Fixed #657
• 47acdc6 Fixed #657
• 1341abb Fixed dynatrace_app_monitoring test case
• 1a9b00e Introduced dynatrace_segment resource and updated config-as-code core (#650)
• c831c1c Fixed #648

v1.75.1

v1.75.1 fixes an issue when updating resources of type dynatrace_iam_policy_boundary. The response code of the REST API was interpreted incorrectly.

Changelog

• 8e34440 v1.75.1
• c1d6a56 Fix: Updating Policy Boundaries may return 204 instead of 201.

v1.75.0

New Resource

• dynatrace_monitored_technologies_python covers configuration to enable/disable Python monitoring
• dynatrace_iam_policy_boundary covers boundaries that can get specified when binding policies to user groups via Account Management API for SaaS Accounts

Bug Fix

• Fixed dynatrace_documents data source from potentially crashing provider
• Fixed export utility from panicking when pulling list of unnamed web applications
• #641 - Fixed dynatrace_custom_service resource from producing non-empty plans
• #643 - Resolved dynatrace_automation_workflow resource missing type attribute

Schema Updates

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

• dynatrace_log_timestamp
• dynatrace_declarative_grouping
• dynatrace_vulnerability_settings
• dynatrace_log_sensitive_data_masking

---

Changelog

• c3176e1 v1.75.0
• 6085d24 Introduced resource dynatrace_policy_boundary (#645)
• abda5de Updated dynatrace_attack_allowlist resource
• 3ae020d Fixed #643
• db0e234 Fixed #643
• 9eba535 Introduced dynatrace_monitored_technologies_python resource
• 157a58c Updated dynatrace_log_sensitive_data_masking resource
• c285d5f Updated dynatrace_vulnerability_settings resource
• 6ed1a5f Updated dynatrace_declarative_grouping resource
• b58befd Updated dynatrace_log_timestamp resource
• 36aab04 Updated resource with version update only
• c48c24c Fixed #641
• daf35ef Fix: Export functionlity potentially panics when pulling a list of entries (web applications) produces unnamed records
• 7487b60 Introduced data source dynatrace_dql as incubator resource
• f7870ac Fix: Data Source dynatrace_documents may crash provider

v1.74.1

New Resources

• dynatrace_security_context covers configuration for security context settings

Bug Fixes

#626 - Exports of dynatrace_json_dashboard_base since v1.72.2 created a required lifecycle meta atribute.

• The REST Endpoint for resource dynatrace_platform_bucket produces unexpected short responses in some customer environments - leading to terraform plan to fail. The environment variable DT_BUCKETS_IGNORE_UNEXPECTED_EOF with value true is a way to prevent these failing plans.

Improvements

#638 - Added documentation for how to configure the provider within .tf code

• Deleting dynatrace_platform_bucket resource works quicker now

---

Changelog

• 870ea11 v1.74.1
• c6867b5 Introduced DT_BUCKETS_IGNORE_UNEXPECTED_EOF
• 3459a68 Deleting platform buckets takes longer than necessary to confirm that the bucket has been deleted
• 1158858 adds documentation how to configure provider in code (#638)
• 855edd9 Disabled test related to #631
• 8807d7b Updated test cases
• 62611ba Introduced dynatrace_security_context resource

v1.74.0

Bug Fixes

#626 - Exports of dynatrace_json_dashboard_base since v1.72.2 created a required lifecycle meta atribute. Older exports didn't work anymore out of the box
#634 - The resource dynatrace_oneagent_default_version is no longer backed by configurable schema. The resource dynatrace_oneagent_updates supersedes that functionality now. dynatrace_oneagent_default_version is still supported for backwards compatibility, but won't have any effects from now on
#629 - Applying dynatrace_slo_v2 produced the error message Provider produced inconsistent result after apply in some environments
#635 - Resource dynatrace_automation_workflow wrongfully requires attribute states within task options

Improvements

• The resource dynatrace_browser_monitor now supports the attributes fetch_requests, xml_http_requests, javascript_errors and timed_actions
  #623 - Allow configuration of anomaly detection for Key User Actions of a dynatrace_web_application

Schema Updates

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

• dynatrace_maintenance
• dynatrace_vulnerability_code
• dynatrace_vulnerability_settings
• dynatrace_appsec_notification
• dynatrace_attribute_allow_list
• dynatrace_davis_anomaly_detectors
• dynatrace_devobs_agent_optin
• dynatrace_log_sensitive_data_masking
• dynatrace_histogram_metrics
• dynatrace_problem_fields
• dynatrace_web_app_custom_injection
• dynatrace_site_reliability_guardian
• dynatrace_app_monitoring
• dynatrace_log_agent_feature_flags
• dynatrace_builtin_process_monitoring
• dynatrace_log_storage
• dynatrace_log_timestamp

Changelog

• 46a012f v1.74.0
• 89190a4 Disabled test for new field - enable v309
• 55aa10e Introduced dynatrace_web_app_auto_injection resource
• f7d9265 Updated dynatrace_attack_allowlist schema version
• 4618c1f Updated dynatrace_log_timestamp resource
• fd1119b Updated dynatrace_log_sensitive_data_masking resource
• dbda63b Updated dynatrace_log_storage resource
• aed7f6b Updated dynatrace_builtin_process_monitoring resource
• 14812dd Updated dynatrace_log_agent_feature_flags resource
• 932b53d Updated dynatrace_app_monitoring resource
• d79ca28 Updated dynatrace_site_reliability_guardian resource
• c7462e1 Fixed #635
• 6b85ae0 Updated resource with version update only
• dfc1740 Ensured that the new properties with default value = true are getting exported correctly
• ddc3818 Fixed generating HCL code for bool with default value = true on all levels of hierarchy
• 6232d62 Fixed #629
• 633d7a6 Resolved #623
• 4075ff0 Updated dynatrace_browser_monitor resource
• c8eee50 added deprecation message to dynatrace_oneagent_default_version
• 9fdedb4 Fixed #634
• 43386c6 Fixed #626