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.

v1.13.2

Release v1.13.2 contains the following improvement:

• Improved documentation for all resources and data sources
  • Links to relevant Dynatrace documentation pages
  • Example usage of Terraform export utility
  • Example usage of Terraform file

Release v1.13.2 fixes the following bug:

• #131: Added credentials vault support for browser monitor keystrokes event

v1.13.1

Release v1.13.1 takes care of the following issues:

• #145/#138: Export of dynatrace_maintenance_window unusable for specific configuration settings
• #136: Data Source dynatrace_synthetic_location did not provide the correct location
• #144: Applying a dynatrace_browser_monitor can lead to crash of the provider
• #121: Export of dynatrace_dashboard_sharing refers hardcoded to the dashboard ID of the source dashboard

In addition to these fixes we have also begun on improving the documentation for supported resources. Check out the current documentation for dynatrace_queue_manager. Please don't hesitate to provide feedback here. We're planning to streamline resource documentation based on how dynatrace_queue_manager looks like right now.

v1.13.0

Release v1.13.0 introduces the following new features:

• Resources
  • dynatrace_ibm_mq_filters covering Setttings > Mainframe > IBM MQ Filters
  • dynatrace_ims_bridges covering Setttings > Mainframe > IBM MQ IMS Bridges
  • dynatrace_queue_sharing_groups covering Setttings > Mainframe > IBM MQ Queue Sharing Groups
  • dynatrace_network_zones covering Setttings > Preferences > Network zones
  • dynatrace_application_detection_rule covering Setttings > Web and Mobile Monitoring > Application Detection
  • dynatrace_alerting superseding the resource dynatrace_alerting_profile. The old REST Endpoint for configuring Alerting Profiles has gotten deprecated recently. You can still continue using the resource dynatrace_alerting_profile within your Terraform Modules as long as the deprecated REST Endpoint is still working in your Dynatrace Environment. We however recommend to switch to the new resource sooner or later. It was unfortunately not possible to switch to the Settings 2.0 Endpoint behind the scenes, because the ID of an Alerting Profile configured via the old endpoint doesn't match the ID of an Alerting Profile configured via Settings 2.0. An automatic schema update was therefore not possible. We're sorry for the inconveniences.
• Data Sources
  • dynatrace_aws_iam_external in order to ease up configuring dynatrace_aws_credentials when role based authentication is getting chosen

Changes and fixes for existing Resources and Data Sources:

• dynatrace_http_monitor allows for configuring authentication for requests now.

v1.12.1

Release v1.12.1 introduces the following Data Sources:

• dynatrace_management_zone allows you to query for Management Zones based on Name.

• dynatrace_service allows you to query for Topology Services based on Service Name and Tags and Tag/Value Pairs.

• dynatrace_host allows you to query for Hosts based on Name and Tags.

• dynatrace_processgroup allows you to query for Process Groups based on Name and Tags.

• dynatrace_process allows you to query for Processes Groups based on Name and Tags.

Upcoming releases wiil introduce the ability to specify Tag/Value Pairs during query for all of the above mentioned Topology Entities.

The following example shows a Data Source querying for a Service named Requests executed in background threads of Code*Service.exe that has a Tag named TerraformKeyTest with any or no value applied and a Tag named TerraformKeyValueTest with the value TestValue. Both Tags need to be present. If multiple Topology Services are matching the given criteria the first one found will be chosen.

data "dynatrace_service" "Test" {
  name = "Requests executed in background threads of Code*Service.exe"
  tags = ["TerraformKeyTest","TerraformKeyValueTest=TestValue"]
}

The ID of the resolved Toplogy Service can now be referred to within any resource.

resource "dynatrace_key_requests" "TerraformTest" {
  service = data.dynatrace_service.Test.id
}

Changes and fixes for existing Resources and Data Sources:

• dynatrace_custom_service now supports the attributes visibility and modifiers officially. These attributes used to be supported via unknowns attribute in the past.
• Dashboard Metadata within the Resource dynatrace_dashboard now supports the attribute consistent_colors.
• The order of rules within Resource dynatrace_alerting_profile is now getting enforced by the Terraform Provider. This turned out to become necessary because the Dynatrace REST API does not guarantee to deliver them in the same order it has received them. You may have to adjust your HCL files to the order the Provider will choose for you. As a rule of thumb here: The JSON formatted representation of the Rules will be ordered alphabetically.
• The order of rules and conditions within Resource dynatrace_management_zone are now getting enforced by the Terraform Provider - for the same reason as for dynatrace_alerting_profile.

v1.11.0

Release v1.11.0 contains the following resources:

• dynatrace_cloudfoundry_credentials - a left over in order to cover configuring credentials for all supported cloud native platforms.

Release v1.11.0 fixes the following bugs.

• #60 - Undescriptive error message when performing export with environment url containing trailing slash
• #97 - Datasource dynatrace_synthetic_locations is missing cloud_platform values
• #108 - Calculated metrics description not getting exported
• #109 - Trailing Slash character in dt_env_url and dt_cluster_url leads to failing REST API Calls
• #110 - Resource dynatrace_azure_credentials doesn't support monitorOnlyExcludingTagPairs
• #112 - Documentation error on dynatrace_k8s_credentials resource for events_field_selectors
• #113 - Alerting profiles event_type_filters change every time
• #116 - user_action_and_session_properties should allow more than 1 property
• #117 - Adding conversion_goals with a user_action goal results in Internal Server Error 500
• #119 - description field not written when adding/changing SLO

v1.10.0

Release v1.10.0 contains the following resources:

• dynatrace_user_group in order to provision user groups for managed clusters.

• dynatrace_user in order to provision users for managed clusters.

• dynatrace_key_requests. I'm aware that configuration is as of now a bit cumbersome because of the absence of a datasource for Services. Dynatrace unfortunately generates a unique identifier for services on every environment. The next release will contain a datasource for topology services, which should make configuring key requests much more convenient.

Release v1.10.0 fixes the following bugs.

• #106
• #107
• #103
• #102
• #99
• #101
• #94
• #91
• #100

v1.9.1

Release v1.9.1 contains the following changes and features:

• Introduced Resource dynatrace_web_application.
• Introduced Resource dynatrace_request_naming.
• Introduced Resource dynatrace_request_namings. This resource is necessary in order to allow for ordering request namings. The current REST API unfortunately doesn't allow for a more convenient way.
• terraform-provider-dynatrace export now doesn't simply omit properties with default values. They are now contained within the generated .tf, but commented out.
• The property owner for Dashboards is now required (was optional before)

v1.8.4

Release v1.8.4 fixes handling of bool properties (like enabled) for the resources dynatrace_browser_monitor and dynatrace_http_monitor.

Please be aware of the fact, that changes to synthetic monitors can be subject to a delay of multiple seconds. Executing terraform plan immediately after terraform apply where updates to resources of type dynatrace_browser_monitor or dynatrace_http_monitor are involved may therefore falsly report that a change set still exists.
A workaround for this behavior will get introduced in future versions of the provider.