Skip to content

Commit d9374af

Browse files
Reinhard-Pilz-DynatraceReinhard-Pilz-Dynatrace
committed
v1.77.0
1 parent 930a6b5 commit d9374af

File tree

8 files changed

+339
-9
lines changed

8 files changed

+339
-9
lines changed

‎docs/index.md‎

Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -31,22 +31,32 @@ Define `DYNATRACE_ENV_URL` for the Dynatrace environment URL.
3131
* SaaS Environments: `https://########.live.dynatrace.com`
3232
* Managed Enviroments: `https://<dynatrace-host>/e/#####################`
3333

34-
Define `DYNATRACE_API_TOKEN` as an [access token](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/access-tokens) with the following permissions.
35-
* **Read configuration** (`ReadConfig`)
36-
* **Write configuration** (`WriteConfig`)
34+
To create an API token with full access to all resources, define `DYNATRACE_API_TOKEN` as an [access token](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/access-tokens) with the following permissions.
3735
* **Read settings** (`settings.read`)
3836
* **Write settings** (`settings.write`)
39-
* **Create and read synthetic monitors, locations, and nodes** (`ExternalSyntheticIntegration`)
37+
* **Read configuration** (`ReadConfig`)
38+
* **Write configuration** (`WriteConfig`)
4039
* **Capture request data** (`CaptureRequestData`)
40+
* **Create and read synthetic monitors, locations, and nodes** (`ExternalSyntheticIntegration`)
41+
* **Create ActiveGate tokens** (`activeGateTokenManagement.create`)
42+
* **Read ActiveGate tokens** (`activeGateTokenManagement.read`)
43+
* **Write ActiveGate tokens** (`activeGateTokenManagement.write`)
44+
* **Read API tokens** (`apiTokens.read`)
45+
* **Write API tokens** (`apiTokens.write`)
46+
* **Read attacks** (`attacks.read`)
47+
* **Write attacks** (`attacks.write`)
4148
* **Read credential vault entries** (`credentialVault.read`)
4249
* **Write credential vault entries** (`credentialVault.write`)
50+
* **Read Entities** (`entities.read`)
51+
* **Write extensions** (`extensions.write`)
52+
* **Read extensions environment configuration** (`extensionEnvironment.read`)
53+
* **Write extensions environment configuration** (`extensionEnvironment.write`)
4354
* **Read network zones** (`networkZones.read`)
4455
* **Write network zones** (`networkZones.write`)
45-
* **Read Entities** (`entities.read`)
4656
* **Read security problems** (`securityProblems.read`)
4757
* **Write security problems** (`securityProblems.write`)
48-
* **Read attacks** (`attacks.read`)
49-
* **Write attacks** (`attacks.write`)
58+
* **Read SLO** (`slo.read`)
59+
* **Write SLO** (`slo.write`)
5060

5161
Configure an [OAuth client](https://dt-url.net/fj43qif) with all of the permissions below to be compatible with all OAuth based Terraform resources, or provide a subset of permissions based off of required use cases - refer to the resource specific pages for additional information.
5262

@@ -66,9 +76,16 @@ Define `DT_CLIENT_ID`, `DT_CLIENT_SECRET`, `DT_ACCOUNT_ID` based off of the crea
6676
* **Read direct-shares** (`document:direct-shares:read`)
6777
* **Write direct-shares** (`document:direct-shares:write`)
6878
* **Delete direct-shares** (`document:direct-shares:delete`)
79+
* **Read OpenPipeline configurations** (`openpipeline:configurations:read`)
80+
* **Write OpenPipeline configurations** (`openpipeline:configurations:write`)
6981
* **View bizevents** (`storage:bizevents:read`)
7082
* **View bucket metadata** (`storage:bucket-definitions:read`)
7183
* **Write buckets** (`storage:bucket-definitions:write`)
84+
* **View Filter-Segments** (`storage:filter-segments:read`)
85+
* **Create and Update Filter-Segments** (`storage:filter-segments:write`)
86+
* **Share Filter-Segments** (`storage:filter-segments:share`)
87+
* **Delete Filter-Segments** (`storage:filter-segments:delete`)
88+
* **Maintain all Filter-Segments on the environment** (`storage:filter-segments:admin`)
7289
* **View users and groups** (`account-idm-read`)
7390
* **Manage users and groups** (`account-idm-write`)
7491
* **View and manage policies** (`iam-policies-management`)

‎docs/resources/credentials.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,14 @@ resource "dynatrace_credentials" "name" {
3131
username = "username"
3232
password = "password"
3333
}
34+
35+
resource "dynatrace_credentials" "root_certificate" {
36+
name = "Root Certificate"
37+
description = "Root certificate for validating Extension 2.0 signatures"
38+
certificate = base64encode(file("certificate.pem"))
39+
format = "PEM"
40+
public = true
41+
}
3442
```
3543

3644
<!-- schema generated by tfplugindocs -->

‎docs/resources/custom_service_order.md‎

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_custom_service_order Resource - terraform-provider-dynatrace"
4+
subcategory: Service Detection"
5+
description: |-
6+
The resource `dynatrace_custom_service_order` covers defining the order of rules defined for custom services
7+
---
8+
9+
# dynatrace_custom_service_order (Resource)
10+
11+
-> This resource requires the API token scopes **Read configuration** (`ReadConfig`) and **Write configuration** (`WriteConfig`)
12+
13+
## Dynatrace Documentation
14+
15+
- Define custom services - https://www.dynatrace.com/support/help/how-to-use-dynatrace/services/custom-services
16+
17+
- Custom services API - https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/service-api/custom-services-api
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_custom_service_order` downloads a resource containing the current order for Custom Services defined in the Dynatrace Environment.
22+
23+
The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
24+
25+
## Resource Example Usage
26+
27+
The example below contains configuration for two custom services defined for .NET applications and two custom services defined for Java applications.
28+
The resource `dynatrace_custom_service_order` defines what order these naming rules should get evaluated in - separated by technology (.NET / Java).
29+
30+
Specifically for this example:
31+
* Custom Services for .NET and Java defined in the Dynatrace Environment that are not managed by Terraform will end up ranked with lower priority than the ones listed within `dynatrace_custom_service_order`
32+
* The order of Custom Services defined in the Dynatrace Environment for Golang, PHP and NodeJS will remain unaffected
33+
34+
-> Be aware of the fact that the resource `dynatrace_custom_service_order` should be treated as a singleton. Maintaining more than one instances of `dynatrace_custom_service_order` within the same Terraform module is not recommended. It will result in non-empty plans.
35+
36+
```terraform
37+
resource "dynatrace_custom_service_order" "this" {
38+
dotnet = [
39+
var.dynatrace_custom_service.dotnet-first.id,
40+
var.dynatrace_custom_service.dotnet-second.id,
41+
]
42+
java = [
43+
var.dynatrace_custom_service.java-first.id,
44+
var.dynatrace_custom_service.java-second.id,
45+
]
46+
}
47+
48+
resource "dynatrace_custom_service" "java-first" {
49+
name = "java-first"
50+
technology = "java"
51+
enabled = true
52+
rule {
53+
...
54+
}
55+
...
56+
queue_entry_point = false
57+
}
58+
59+
resource "dynatrace_custom_service" "java-second" {
60+
name = "java-second"
61+
technology = "java"
62+
enabled = true
63+
rule {
64+
...
65+
}
66+
...
67+
queue_entry_point = false
68+
}
69+
70+
resource "dynatrace_custom_service" "dotnet-first" {
71+
name = "dotnet-first"
72+
technology = "dotNet"
73+
enabled = true
74+
rule {
75+
...
76+
}
77+
...
78+
queue_entry_point = false
79+
}
80+
81+
resource "dynatrace_custom_service" "dotnet-second" {
82+
name = "dotnet-second"
83+
technology = "dotNet"
84+
enabled = true
85+
rule {
86+
...
87+
}
88+
...
89+
queue_entry_point = false
90+
}
91+
```
92+
93+
<!-- schema generated by tfplugindocs -->
94+
## Schema
95+
96+
### Optional
97+
98+
- `dotnet` (List of String) The IDs of Custom Services for .Net in the desired order
99+
- `golang` (List of String) The IDs of Custom Services for Golang in the desired order
100+
- `java` (List of String) The IDs of Custom Services for Java in the desired order
101+
- `nodejs` (List of String) The IDs of Custom Services for NodeJS in the desired order
102+
- `php` (List of String) The IDs of Custom Services for PHP in the desired order
103+
104+
### Read-Only
105+
106+
- `id` (String) The ID of this resource.
107+

‎docs/resources/host_anomalies_v2.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ Required:
182182

183183
Optional:
184184

185-
- `on_graceful_shutdowns` (String) Graceful host shutdowns
185+
- `on_graceful_shutdowns` (String) Graceful host shutdowns. Possible values: `DONT_ALERT_ON_GRACEFUL_SHUTDOWN`, `ALERT_ON_GRACEFUL_SHUTDOWN`
186186

187187

188188
<a id="nestedblock--host--high_cpu_saturation_detection"></a>

‎docs/resources/host_naming_order.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_host_naming_order Resource - terraform-provider-dynatrace"
4+
subcategory: Host Monitoring"
5+
description: |-
6+
The resource `dynatrace_host_naming_order` covers defining the order of rules defined for host naming
7+
---
8+
9+
# dynatrace_host_naming_order (Resource)
10+
11+
-> This resource requires the API token scopes **Read configuration** (`ReadConfig`) and **Write configuration** (`WriteConfig`)
12+
13+
## Dynatrace Documentation
14+
15+
- Service naming rules - https://www.dynatrace.com/support/help/how-to-use-dynatrace/services/service-detection-and-naming/customize-service-naming
16+
17+
- Conditional naming API - https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/conditional-naming
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_host_naming_order` downloads an ordered list of service naming rule IDs
22+
23+
The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
24+
25+
## Resource Example Usage
26+
27+
The example below contains configuration for two host naming rules.
28+
The resource `dynatrace_host_naming_order` defines what order these naming rules should get evaluated in.
29+
30+
In case the Dynatrace environment contains additional host naming rules that are not managed by Terraform, these
31+
naming rules will end up ranked with lower priority than the ones listed within the `dynatrace_host_naming_order` resource.
32+
33+
-> Be aware of the fact that the resource `dynatrace_host_naming_order` should be treated as a singleton. Maintaining more than one instances of `dynatrace_host_naming_order` within the same Terraform module is not recommended. It will result in non-empty plans.
34+
35+
```terraform
36+
resource "dynatrace_host_naming_order" "this" {
37+
naming_rule_ids = [
38+
dynatrace_host_naming.first.id,
39+
dynatrace_host_naming.second.id,
40+
]
41+
}
42+
43+
resource "dynatrace_host_naming" "first" {
44+
name = "first"
45+
enabled = true
46+
...
47+
}
48+
49+
resource "dynatrace_host_naming" "second" {
50+
name = "second"
51+
enabled = true
52+
...
53+
}
54+
```
55+
56+
<!-- schema generated by tfplugindocs -->
57+
## Schema
58+
59+
### Optional
60+
61+
- `naming_rule_ids` (List of String) The IDs of the naming rules to define the order for
62+
63+
### Read-Only
64+
65+
- `id` (String) The ID of this resource.
66+

‎docs/resources/processgroup_naming_order.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_processgroup_naming_order Resource - terraform-provider-dynatrace"
4+
subcategory: "Process Group Monitoring"
5+
description: |-
6+
The resource `dynatrace_processgroup_naming_order` covers defining the order of rules defined for process group naming
7+
---
8+
9+
# dynatrace_processgroup_naming_order (Resource)
10+
11+
-> This resource requires the API token scopes **Read configuration** (`ReadConfig`) and **Write configuration** (`WriteConfig`)
12+
13+
## Dynatrace Documentation
14+
15+
- Process group naming - https://www.dynatrace.com/support/help/how-to-use-dynatrace/process-groups/configuration/pg-naming
16+
17+
- Conditional naming API - https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/conditional-naming
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_processgroup_naming_order` downloads an ordered list of process group naming rule IDs
22+
23+
The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
24+
25+
## Resource Example Usage
26+
27+
The example below contains configuration for two process group naming rules.
28+
The resource `dynatrace_processgroup_naming_order` defines what order these naming rules should get evaluated in.
29+
30+
In case the Dynatrace environment contains additional process group naming rules that are not managed by Terraform, these
31+
naming rules will end up ranked with lower priority than the ones listed within the `dynatrace_processgroup_naming_order` resource.
32+
33+
-> Be aware of the fact that the resource `dynatrace_processgroup_naming_order` should be treated as a singleton. Maintaining more than one instances of `dynatrace_processgroup_naming_order` within the same Terraform module is not recommended. It will result in non-empty plans.
34+
35+
```terraform
36+
resource "dynatrace_processgroup_naming_order" "process_group_naming_order" {
37+
naming_rule_ids = [
38+
dynatrace_processgroup_naming.first.id,
39+
dynatrace_processgroup_naming.second.id,
40+
]
41+
}
42+
43+
resource "dynatrace_processgroup_naming" "first" {
44+
name = "first-one"
45+
enabled = true
46+
...
47+
}
48+
49+
resource "dynatrace_processgroup_naming" "second" {
50+
name = "second-one"
51+
enabled = true
52+
...
53+
}
54+
```
55+
56+
<!-- schema generated by tfplugindocs -->
57+
## Schema
58+
59+
### Optional
60+
61+
- `naming_rule_ids` (List of String) The IDs of the naming rules to define the order for
62+
63+
### Read-Only
64+
65+
- `id` (String) The ID of this resource.
66+

‎docs/resources/service_naming_order.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_service_naming_order Resource - terraform-provider-dynatrace"
4+
subcategory: Service Monitoring"
5+
description: |-
6+
The resource `dynatrace_service_naming_order` covers defining the order of rules defined for service naming
7+
---
8+
9+
# dynatrace_service_naming_order (Resource)
10+
11+
-> This resource requires the API token scopes **Read configuration** (`ReadConfig`) and **Write configuration** (`WriteConfig`)
12+
13+
## Dynatrace Documentation
14+
15+
- Service naming rules - https://www.dynatrace.com/support/help/how-to-use-dynatrace/services/service-detection-and-naming/customize-service-naming
16+
17+
- Conditional naming API - https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/conditional-naming
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_service_naming_order` downloads an ordered list of service naming rule IDs
22+
23+
The full documentation of the export feature is available [here](https://dt-url.net/h203qmc).
24+
25+
## Resource Example Usage
26+
27+
The example below contains configuration for two service naming rules.
28+
The resource `dynatrace_service_naming_order` defines what order these naming rules should get evaluated in.
29+
30+
In case the Dynatrace environment contains additional service naming rules that are not managed by Terraform, these
31+
naming rules will end up ranked with lower priority than the ones listed within the `dynatrace_service_naming_order` resource.
32+
33+
-> Be aware of the fact that the resource `dynatrace_service_naming_order` should be treated as a singleton. Maintaining more than one instances of `dynatrace_service_naming_order` within the same Terraform module is not recommended. It will result in non-empty plans.
34+
35+
```terraform
36+
resource "dynatrace_service_naming_order" "this" {
37+
naming_rule_ids = [
38+
dynatrace_service_naming.first.id,
39+
dynatrace_service_naming.second.id,
40+
]
41+
}
42+
43+
resource "dynatrace_service_naming" "first" {
44+
name = "first"
45+
enabled = true
46+
...
47+
}
48+
49+
resource "dynatrace_service_naming" "second" {
50+
name = "second"
51+
enabled = true
52+
...
53+
}
54+
```
55+
56+
<!-- schema generated by tfplugindocs -->
57+
## Schema
58+
59+
### Optional
60+
61+
- `naming_rule_ids` (List of String) The IDs of the naming rules to define the order for
62+
63+
### Read-Only
64+
65+
- `id` (String) The ID of this resource.
66+

‎provider/version/version.go‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@
1717

1818
package version
1919

20-
const Current = "1.76.0"
20+
const Current = "1.77.0"

0 commit comments

Comments
 (0)