You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,9 @@ The value of `DYNATRACE_API_TOKEN` needs to be an API Token with the following p
61
61
* Required for writing attack security configuration.
62
62
63
63
Alternatively - but not recommended for security reasons you can also add configuration options within your Terraform Module.
64
+
65
+
!> Specifying credentials for Dynatrace environments is considered highly problematic from a security standpoint. Especially in production environments the environment variables DYNATRACE_ENV_URL and DYNATRACE_API_TOKEN are the recommended way to go when it comes to configuring the Dynatrace Terraform Provider. There exists usually never a good reason to specify credentials inline.
Copy file name to clipboardExpand all lines: templates/index.md.tmpl
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,9 @@ The value of `DYNATRACE_API_TOKEN` needs to be an API Token with the following p
61
61
* Required for writing attack security configuration.
62
62
63
63
Alternatively - but not recommended for security reasons you can also add configuration options within your Terraform Module.
64
+
65
+
!> Specifying credentials for Dynatrace environments is considered highly problematic from a security standpoint. Especially in production environments the environment variables DYNATRACE_ENV_URL and DYNATRACE_API_TOKEN are the recommended way to go when it comes to configuring the Dynatrace Terraform Provider. There exists usually never a good reason to specify credentials inline.
0 commit comments