v1.64.0

Author: kishikawa12

docs/resources/cloudapp_workloaddetection.md

@@ -62,14 +62,22 @@ resource "dynatrace_cloudapp_workloaddetection" "cloud_app_workload_detection" {
 - `cloud_foundry` (Block List, Min: 1, Max: 1) Enable this setting to get 
  * Processes of Cloud Foundry application instances merged into process groups by Cloud Foundry application. 
  *  Container resource metrics (Container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). (see [below for nested schema](#nestedblock--cloud_foundry))
-- `docker` (Block List, Min: 1, Max: 1) Enable this setting for plain Docker environments to get 
- * Container resource metrics (Container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). (see [below for nested schema](#nestedblock--docker))
+- `docker` (Block List, Min: 1, Max: 1) Enable this setting for plain Docker and Podman environments to get 
+ * Container resource metrics (Container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). 
+ * Docker support requires OneAgent 1.257+. 
+ * Podman support requires OneAgent 1.267+. (see [below for nested schema](#nestedblock--docker))
 - `kubernetes` (Block List, Min: 1, Max: 1) Enable this setting to get 
  * Insights into your Kubernetes namespaces, workloads and pods (cloud application namespace, cloud application and cloud application instance and entities). 
  * Container resource metrics (container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). 
  * Similar workloads merged into process groups based on defined rules (see below). 
  * Version detection for services that run in Kubernetes workloads. (see [below for nested schema](#nestedblock--kubernetes))
 
+### Optional
+
+- `serverless` (Block List, Max: 1) Enable this setting to 
+ * Detect containers based on captured cloud-vendor metadata such as e.g. AWS ECS / Fargate, Azure Container Apps, [and many more](https://dt-url.net/2m02q7b).
+ * Container resource metrics (Container group instance entities) and [related screens](https://www.dynatrace.com/support/help/shortlink/container-groups). (see [below for nested schema](#nestedblock--serverless))
+
 ### Read-Only
 
 - `id` (String) The ID of this resource.
@@ -141,4 +149,15 @@ Required:
 Optional:
 
 - `namespace` (String) Namespace name
+
+
+
+
+
+<a id="nestedblock--serverless"></a>
+### Nested Schema for `serverless`
+
+Required:
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
 

docs/resources/hub_permissions.md

@@ -38,8 +38,8 @@ resource "dynatrace_hub_permissions" "#name#" {
 
 ### Required
 
-- `description` (String) Description
-- `email` (String) Email
+- `description` (String) Name
+- `email` (String) Contact Email
 
 ### Read-Only
 

docs/resources/log_timestamp.md

@@ -53,7 +53,8 @@ resource "dynatrace_log_timestamp" "#name#" {
 
 ### Optional
 
-- `date_search_limit` (Number) (v1.275) Defines the number of characters in every log line (starting from the first character in the line) where the timestamp is searched.
+- `date_search_limit` (Number) Defines the number of characters in every log line (starting from the first character in the line) where the timestamp is searched.
+- `entry_boundary` (Block List, Max: 1) Optional field. Enter a fragment of the line text that starts the entry. No support for wildcards - the text is treated literally. (see [below for nested schema](#nestedblock--entry_boundary))
 - `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
 - `matchers` (Block List, Max: 1) no documentation available (see [below for nested schema](#nestedblock--matchers))
 - `scope` (String) The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
@@ -62,6 +63,14 @@ resource "dynatrace_log_timestamp" "#name#" {
 
 - `id` (String) The ID of this resource.
 
+<a id="nestedblock--entry_boundary"></a>
+### Nested Schema for `entry_boundary`
+
+Optional:
+
+- `pattern` (String) no documentation available
+
+
 <a id="nestedblock--matchers"></a>
 ### Nested Schema for `matchers`
 

docs/resources/platform_bucket.md

@@ -39,6 +39,15 @@ provider "dynatrace" {
 ```
 -> In order to handle credentials in a secure manner we recommend to use the environment variables `DYNATRACE_AUTOMATION_CLIENT_ID` and `DYNATRACE_AUTOMATION_CLIENT_SECRET` as an alternative.
 
+## Environment Variables (Optional)
+
+There may be a delay for this resource to be fully available as a dependency for a subsequent resource. E.g. Utilizing this resource and `dynatrace_log_buckets` together.
+ 
+A default polling mechanism exists to validate the creation but may require tweaking due to load. The following environment variables can be used to fine tune these settings.
+
+- `DT_BUCKETS_RETRIES` (Default: 180, Max: 360) configures the maximum attempts to confirm that the operation (create, update or delete) has succeeded and was completed on the server side. There is a two second delay between consecutive attempts, therefore the check completes with at most 720 seconds with the maximum setting.
+- `DT_BUCKETS_NUM_SUCCESSES` (Default: 10, Max: 50) configures the number of successful consecutive retries expected, this applies to creating the resource only.
+
 ## Resource Example Usage
 
 ```terraform

provider/version/version.go

@@ -17,4 +17,4 @@
 
 package version
 
-const Current = "1.63.0"
+const Current = "1.64.0"