v1.61.0

kishikawa12 · kishikawa12 · commit d003757eacef · 2024-07-26T12:15:12.000-04:00
diff --git a/docs/resources/automation_workflow_jira.md b/docs/resources/automation_workflow_jira.md
@@ -45,7 +45,7 @@ resource "dynatrace_automation_workflow_jira" "#name#"{
 
 ### Optional
 
-- `insert_after` (String) Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
+- `insert_after` (String, Deprecated) Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
 - `password` (String, Sensitive) Password of the Jira user
 - `token` (String, Sensitive) Token for the selected authentication type
 - `user` (String) Username or E-Mail address
diff --git a/docs/resources/automation_workflow_slack.md b/docs/resources/automation_workflow_slack.md
@@ -43,7 +43,7 @@ resource "dynatrace_automation_workflow_slack" "#name#" {
 
 ### Optional
 
-- `insert_after` (String) Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
+- `insert_after` (String, Deprecated) Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
 
 ### Read-Only
 
diff --git a/docs/resources/business_events_oneagent.md b/docs/resources/business_events_oneagent.md
@@ -3,7 +3,7 @@ layout: ""
 page_title: dynatrace_business_events_oneagent Resource - terraform-provider-dynatrace"
 subcategory: "Business Events"
 description: |-
-  The resource `dynatrace_business_events_oneagent` covers configuration for OneAgent business events
+  The resource `dynatrace_business_events_oneagent` covers configuration for OneAgent business events based on incoming HTTP requests
 ---
 
 # dynatrace_business_events_oneagent (Resource)
@@ -18,7 +18,7 @@ description: |-
 
 ## Export Example Usage
 
-- `terraform-provider-dynatrace -export dynatrace_business_events_oneagent` downloads all existing OneAgent business events
+- `terraform-provider-dynatrace -export dynatrace_business_events_oneagent` downloads all existing OneAgent business events based on incoming HTTP requests
 
 The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
 
diff --git a/docs/resources/business_events_oneagent_outgoing.md b/docs/resources/business_events_oneagent_outgoing.md
@@ -0,0 +1,200 @@
+---
+layout: ""
+page_title: dynatrace_business_events_oneagent_outgoing Resource - terraform-provider-dynatrace"
+subcategory: "Business Events"
+description: |-
+  The resource `dynatrace_business_events_oneagent_outgoing` covers configuration for OneAgent business events based on outgoing HTTP requests
+---
+
+# dynatrace_business_events_oneagent_outgoing (Resource)
+
+-> This resource requires the API token scopes **Read settings** (`settings.read`) and **Write settings** (`settings.write`)
+
+## Dynatrace Documentation
+
+- Business event capture - https://www.dynatrace.com/support/help/platform-modules/business-analytics/ba-events-capturing#report-business-event-oneagent
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:bizevents.http.outgoingg`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_business_events_oneagent_outgoing` downloads all existing OneAgent business events based on outgoing HTTP requests
+
+The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_business_events_oneagent_outgoing" "#name#" {
+  enabled      = true
+  rule_name    = "#name#"
+  scope        = "environment"
+  event {
+    category {
+      source      = "Category 1"
+      source_type = "constant.string"
+    }
+    data {
+      event_data_field_complex {
+        name = "Field 1"
+        source {
+          path        = "Path 1"
+          source_type = "request.body"
+        }
+      }
+    }
+    provider {
+      source      = "Provider 1"
+      source_type = "constant.string"
+    }
+    type {
+      source      = "Type 1"
+      source_type = "constant.string"
+    }
+  }
+  triggers {
+    trigger {
+      type           = "EQUALS"
+      case_sensitive = false
+      value          = "Terraform"
+      source {
+        data_source = "request.path"
+      }
+    }
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+- `event` (Block List, Min: 1, Max: 1) Event meta data (see [below for nested schema](#nestedblock--event))
+- `rule_name` (String) Rule name
+- `triggers` (Block List, Min: 1, Max: 1) Define conditions to trigger business events from incoming web requests. Triggers are connected by AND logic per capture rule. If you set multiple trigger rules, all of them need to be fulfilled to capture a business event. (see [below for nested schema](#nestedblock--triggers))
+
+### Optional
+
+- `insert_after` (String) Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
+- `scope` (String) The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--event"></a>
+### Nested Schema for `event`
+
+Required:
+
+- `category` (Block List, Min: 1, Max: 1) Event category (see [below for nested schema](#nestedblock--event--category))
+- `provider` (Block List, Min: 1, Max: 1) Event provider (see [below for nested schema](#nestedblock--event--provider))
+- `type` (Block List, Min: 1, Max: 1) Event type (see [below for nested schema](#nestedblock--event--type))
+
+Optional:
+
+- `data` (Block List, Max: 1) Additional attributes for the business event. (see [below for nested schema](#nestedblock--event--data))
+
+<a id="nestedblock--event--category"></a>
+### Nested Schema for `event.category`
+
+Required:
+
+- `source_type` (String) Possible Values: `Constant_string`, `Request_body`, `Request_headers`, `Request_method`, `Request_parameters`, `Request_path`, `Request_url`, `Response_body`, `Response_headers`, `Response_statusCode`
+
+Optional:
+
+- `path` (String) [See our documentation](https://dt-url.net/ei034bx)
+- `source` (String) Fixed value
+
+
+<a id="nestedblock--event--provider"></a>
+### Nested Schema for `event.provider`
+
+Required:
+
+- `source_type` (String) Possible Values: `Constant_string`, `Request_body`, `Request_headers`, `Request_method`, `Request_parameters`, `Request_path`, `Request_url`, `Response_body`, `Response_headers`, `Response_statusCode`
+
+Optional:
+
+- `path` (String) [See our documentation](https://dt-url.net/ei034bx)
+- `source` (String) Fixed value
+
+
+<a id="nestedblock--event--type"></a>
+### Nested Schema for `event.type`
+
+Required:
+
+- `source_type` (String) Possible Values: `Constant_string`, `Request_body`, `Request_headers`, `Request_method`, `Request_parameters`, `Request_path`, `Request_url`, `Response_body`, `Response_headers`, `Response_statusCode`
+
+Optional:
+
+- `path` (String) [See our documentation](https://dt-url.net/ei034bx)
+- `source` (String) Fixed value
+
+
+<a id="nestedblock--event--data"></a>
+### Nested Schema for `event.data`
+
+Required:
+
+- `event_data_field_complex` (Block Set, Min: 1) (see [below for nested schema](#nestedblock--event--data--event_data_field_complex))
+
+<a id="nestedblock--event--data--event_data_field_complex"></a>
+### Nested Schema for `event.data.event_data_field_complex`
+
+Required:
+
+- `name` (String) Field name to be added to data.
+- `source` (Block List, Min: 1, Max: 1) no documentation available (see [below for nested schema](#nestedblock--event--data--event_data_field_complex--source))
+
+<a id="nestedblock--event--data--event_data_field_complex--source"></a>
+### Nested Schema for `event.data.event_data_field_complex.source`
+
+Required:
+
+- `source_type` (String) Possible Values: `Constant_string`, `Request_body`, `Request_headers`, `Request_method`, `Request_parameters`, `Request_path`, `Request_url`, `Response_body`, `Response_headers`, `Response_statusCode`
+
+Optional:
+
+- `path` (String) [See our documentation](https://dt-url.net/ei034bx)
+- `source` (String) Fixed value
+
+
+
+
+
+<a id="nestedblock--triggers"></a>
+### Nested Schema for `triggers`
+
+Required:
+
+- `trigger` (Block Set, Min: 1) (see [below for nested schema](#nestedblock--triggers--trigger))
+
+<a id="nestedblock--triggers--trigger"></a>
+### Nested Schema for `triggers.trigger`
+
+Required:
+
+- `source` (Block List, Min: 1, Max: 1) no documentation available (see [below for nested schema](#nestedblock--triggers--trigger--source))
+- `type` (String) Possible Values: `CONTAINS`, `ENDS_WITH`, `EQUALS`, `EXISTS`, `N_CONTAINS`, `N_ENDS_WITH`, `N_EQUALS`, `N_EXISTS`, `N_STARTS_WITH`, `STARTS_WITH`
+
+Optional:
+
+- `case_sensitive` (Boolean) Case sensitive
+- `value` (String) no documentation available
+
+<a id="nestedblock--triggers--trigger--source"></a>
+### Nested Schema for `triggers.trigger.source`
+
+Required:
+
+- `data_source` (String) Possible Values: `Request_body`, `Request_headers`, `Request_method`, `Request_parameters`, `Request_path`, `Request_url`, `Response_body`, `Response_headers`, `Response_statusCode`
+
+Optional:
+
+- `path` (String) [See our documentation](https://dt-url.net/ei034bx)
+ 
diff --git a/docs/resources/credentials.md b/docs/resources/credentials.md
@@ -43,6 +43,7 @@ resource "dynatrace_credentials" "name" {
 ### Optional
 
 - `allow_contextless_requests` (Boolean) Allow ad-hoc functions to access the credential details (requires the APP_ENGINE scope).
+- `allowed_entities` (Block List, Max: 1) The set of entities allowed to use the credential. (see [below for nested schema](#nestedblock--allowed_entities))
 - `certificate` (String) The certificate in the string format.
 - `credential_usage_summary` (Block List, Max: 2, Deprecated) The list contains summary data related to the use of credentials (see [below for nested schema](#nestedblock--credential_usage_summary))
 - `description` (String) A short description of the credentials set
@@ -60,6 +61,23 @@ resource "dynatrace_credentials" "name" {
 
 - `id` (String) The ID of this resource.
 
+<a id="nestedblock--allowed_entities"></a>
+### Nested Schema for `allowed_entities`
+
+Required:
+
+- `entity` (Block Set, Min: 1) The set of entities allowed to use the credential. (see [below for nested schema](#nestedblock--allowed_entities--entity))
+
+<a id="nestedblock--allowed_entities--entity"></a>
+### Nested Schema for `allowed_entities.entity`
+
+Optional:
+
+- `id` (String) ID of the entity
+- `type` (String) Type of entity. Possible values: `USER`, `APPLICATION`, `UNKNOWN`
+
+
+
 <a id="nestedblock--credential_usage_summary"></a>
 ### Nested Schema for `credential_usage_summary`
 
diff --git a/docs/resources/disk_edge_anomaly_detectors.md b/docs/resources/disk_edge_anomaly_detectors.md
@@ -49,14 +49,14 @@ resource "dynatrace_disk_edge_anomaly_detectors" "#name#" {
       metadata_value = "ExampleValue"
     }
   }
-  host_metadata_conditions {
-    host_metadata_condition {
-      host_metadata_condition {
-        metadata_condition = "$contains(terraform)"
-        metadata_key       = "ExampleKey"
-      }
-    }
-  }
+  # host_metadata_conditions { # Disabling until v297
+  #   host_metadata_condition {
+  #     host_metadata_condition {
+  #       metadata_condition = "$contains(terraform)"
+  #       metadata_key       = "ExampleKey"
+  #     }
+  #   }
+  # }
 }
 ```
 
@@ -74,6 +74,7 @@ resource "dynatrace_disk_edge_anomaly_detectors" "#name#" {
 - `disk_name_filters` (Set of String) Disk will be included in this policy if **any** of the filters match
 - `event_properties` (Block List, Max: 1) Set of additional key-value properties to be attached to the triggered event. (see [below for nested schema](#nestedblock--event_properties))
 - `host_metadata_conditions` (Block List, Max: 1) The policy will be enabled if **all** conditions are met (see [below for nested schema](#nestedblock--host_metadata_conditions))
+- `insert_after` (String) Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
 - `operating_system` (Set of String) Select the operating systems on which policy should be applied
 - `scope` (String) The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
 
@@ -178,4 +179,8 @@ Available logic operations:
 
 Brackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**
 - `metadata_key` (String) Key
+
+Optional:
+
+- `key_must_exist` (Boolean) When enabled, the condition requires a metadata key to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.
  
diff --git a/docs/resources/oneagent_default_mode.md b/docs/resources/oneagent_default_mode.md
@@ -0,0 +1,43 @@
+---
+layout: ""
+page_title: dynatrace_oneagent_default_mode Resource - terraform-provider-dynatrace"
+subcategory: "Environment Settings"
+description: |-
+  The resource `dynatrace_oneagent_default_mode` covers configuration for OneAgent default mode
+---
+
+# dynatrace_oneagent_default_mode (Resource)
+
+-> This resource requires the API token scopes **Read settings** (`settings.read`) and **Write settings** (`settings.write`)
+
+## Dynatrace Documentation
+
+- Application Security and monitoring modes - https://docs.dynatrace.com/docs/platform-modules/application-security/getting-started/monitoring-modes
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:deployment.oneagent.default-mode`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_oneagent_default_mode` downloads existing OneAgent default mode configuration
+
+The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_oneagent_default_mode" "#name#" {
+  default_mode = "FULL_STACK"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `default_mode` (String) Possible Values: `DISCOVERY`, `FULL_STACK`, `INFRASTRUCTURE`
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+ 
diff --git a/docs/resources/os_services.md b/docs/resources/os_services.md
@@ -156,7 +156,7 @@ Use one of the following values as a parameter for this condition:
 
 Required:
 
-- `metadata_condition` (String) This string has to match a required format. See [OS services monitoring](https://dt-url.net/vl03xzk).
+- `metadata_condition` (String) This string has to match a required format.
 
 - `$contains(production)` – Matches if `production` appears anywhere in the host metadata value.
 - `$eq(production)` – Matches if `production` matches the host metadata value exactly.
@@ -171,6 +171,10 @@ Available logic operations:
 Brackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**
 - `metadata_key` (String) Key
 
+Optional:
+
+- `key_must_exist` (Boolean) When enabled, the condition requires a metadata key to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.
+
 
 
 
@@ -225,7 +229,7 @@ Use one of the following values as a parameter for this condition:
 
 Required:
 
-- `metadata_condition` (String) This string has to match a required format. See [OS services monitoring](https://dt-url.net/vl03xzk).
+- `metadata_condition` (String) This string has to match a required format.
 
 - `$contains(production)` – Matches if `production` appears anywhere in the host metadata value.
 - `$eq(production)` – Matches if `production` matches the host metadata value exactly.
@@ -240,6 +244,10 @@ Available logic operations:
 Brackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**
 - `metadata_key` (String) Key
 
+Optional:
+
+- `key_must_exist` (Boolean) When enabled, the condition requires a metadata key to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.
+
 
 
 
diff --git a/docs/resources/process_availability.md b/docs/resources/process_availability.md
diff --git a/provider/version/version.go b/provider/version/version.go
