v1.14.0

New Resources

• dynatrace_frequent_issues allows to configure whether to detect frequent issues within Applications, Transactions and Services and Infrastructure.

Improved Datasources

• The Datasource dynatrace_credentials now allows to query for credentials from the Credentials Vault using Name, Type and/or Scope.

Resources for Settings 2.0

A couple of REST Endpoints have gotten deprecated within the Dynatrace REST API in favor of alternative Endpoints using Settings 2.0.
These deprecated REST Endpoints are still working as expected - but new capabilities won't be available through them.
The same thing applies to the resources available when using this Terraform Provider. Resources addressing an already deprecated REST Endpoint are still usable. In order to benefit from new functionality it will be necessary to migrate to Resources that are addressing the new Endpoints.
The following Resources have been introduced as Settings 2.0 alternatives:

• dynatrace_maintenance allows for configuring Maintenance Windows via Settings 2.0
  • dynatrace_maintenance_window is still supported
• The resource dynatrace_notification is still supported. In order to benefit from additional features available via Settings 2.0 we recommend to migrate to these resources:
  • dynatrace_ansible_tower_notification
  • dynatrace_email_notification
  • dynatrace_jira_notification
  • dynatrace_ops_genie_notification
  • dynatrace_pager_duty_notification
  • dynatrace_service_now_notification
  • dynatrace_slack_notification
  • dynatrace_trello_notification
  • dynatrace_victor_ops_notification
  • dynatrace_webhook_notification
  • dynatrace_xmatters_notification

Bug Fixes

• Automatic Tests for Web Applications
  • Because of a race condition these tests used to fail when executed via CI while passing when executed manually
• The ordering of the rules within the resource dynatrace_auto_tag was not predictable in all cases.
• You don't have to specify the permissions within the resource dynatrace_dashboard_sharing in a specific order anymore.
  • Existing Terraform States for dashboard_sharing are likely listing these resources to be re-created when using 1.14.0. You can safely approve that change. Release 1.14.0 computes a different ID for these resource now.