chore(deps): update terraform dynatrace to v1.70.0 #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.58.5
->1.70.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dynatrace-oss/terraform-provider-dynatrace (dynatrace)
v1.70.0
Compare Source
New Resources
dynatrace_cloud_development_environments
covers configuration for cloud development environmentsdynatrace_kubernetes_spm
covers configuration for Kubernetes security posture managementdynatrace_log_agent_feature_flags
covers configuration for log agent feature flagsdynatrace_problem_record_propagation_rules
covers configuration for problem record propagation rulesImprovements
Bug Fixes
dynatrace_tenant
data source docsinsert_after
no longer downloads all resources with-ref
dynatrace_automation_workflow
dynatrace_document
dynatrace_iam_policies
data sourcedynatrace_automation_workflow
-flat
and-ref
dynatrace_autotag_rules
when used within a moduleSchema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_k8s_monitoring
dynatrace_log_storage
dynatrace_log_sensitive_data_masking
dynatrace_log_timestamp
Changelog
fd23293
v1.70.0d11c425
Updated supported resources docc83174c
Fixed #586663ef44
Fixed #5875937f2f
Fixed #577ba5075f
Fixed #5854168b63
Merge branch 'main' of https://github.com/dynatrace-oss/terraform-provider-dynatrace6c6a483
Introduceddynatrace_problem_record_propagation_rules
resourced5da779
Introducedynatrace_log_agent_feature_flags
resourcea4da007
Fixed #583 and enabled automatic tests for documentsafdafc8
Introduceddynatrace_kubernetes_spm
resource4df959c
Solution for #578 (#584)e99c1cf
Feat/tflog final (#580)af13e5e
Fixed #579d0c07b5
Introduceddynatrace_cloud_development_environments
resource912a151
Updateddynatrace_log_timestamp
resource479160e
Updateddynatrace_log_sensitive_data_masking
resource129d48d
Updateddynatrace_log_storage
resource4463ca6
Disabled DDUPools test case8e852a6
Updateddynatrace_k8s_monitoring
resource3aeada5
Updated resource with version update onlydfa6963
Added supported resources reference to registry554fee4
Introduced supported resources reference pagedf2289e
Fixed #570b961db0
preventing Provider Test to run when Integration tests are runningeb5ba74
Fix: Direct Shares for documents didn't get applied correctly3288930
Migrated documents client to the one shared by configuration-as-code-core63586ae
Updated documentation fordynatrace_hub_extension_config
v1.69.1
Compare Source
Improvements
terraform-provider-Dynatrace -export dynatrace_json_dashboard -exclude dynatrace_dashboard_sharing
dynatrace_report
is no longer getting exported by default. It depends ondynatrace_json_dashboard
, which is also excluded by default.dynatrace_host_monitoring_mode
is now utilizing different REST endpoints. Configuring the Monitoring Mode of an Agent differs significantly from other settings. See the documentation of dynatrace_host_monitoring_mode for details about limitationsDYNATRACE_LOG_HTTP
tostdout
will capture HTTP traffic using Terraform Debug Logging instead of an external fileBug Fixes
dynatrace_mgmz_permission
didn't support all possible permssionsDYNATRACE_CLUSTER_URL
andDYNATRACE_CLUSTER_API_TOKEN
dynatrace_hub_extension_config
with an invalid ID within the state produced an unexpected error message instead of 404Schema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_discovery_default_rules
dynatrace_log_custom_source
dynatrace_log_oneagent
dynatrace_log_storage
dynatrace_log_sensitive_data_masking
dynatrace_log_timestamp
dynatrace_declarative_grouping
dynatrace_credentials
dynatrace_request_attribute
Changelog
fdadb8a
v1.69.1cc40f5a
Updateddynatrace_request_attribute
resourceba88d17
Deleting removed endpoint /calculatedMetrics/log245ef20
Updateddynatrace_credentials
resource5fed677
Updateddynatrace_declarative_grouping
resourcefbeb108
v1.69.156b5c16
Updateddynatrace_web_app_enablement
resourcea895ad7
Updateddynatrace_mobile_app_enablement
resource7e69c6f
Updateddynatrace_log_timestamp
resource7c693f5
Updateddynatrace_log_sensitive_data_masking
resource5e145cd
Updateddynatrace_log_storage
resourcef767ac6
Updateddynatrace_log_oneagent
resource454e3df
Updateddynatrace_log_custom_source
resourced508f24
Updateddynatrace_discovery_default_rules
resourced1ed36e
Updated resource with version update only8fda994
Introduced stdout logging with TF_LOG (#566)e593992
Fixed #550eabafa8
Fixed unexpected error during Delete for #560146cfd7
[Export] Excludeddynatrace_report
from default export (dependency to dashboards)c875b09
Fixed test cased5afc87
removed debug output8e4d0a9
Fixed #564308e17d
Fixed #563ac7e712
Fixed #562v1.69.0
Compare Source
New Resources
dynatrace_openpipeline_logs
covers configuration of OpenPipeline for Logsdynatrace_openpipeline_events
covers configuration of OpenPipeline for Eventsdynatrace_openpipeline_business_events
covers configuration of OpenPipeline for Business Eventsdynatrace_openpipeline_sdlc_events
covers configuration of OpenPipeline for Software Development Lifecycle Eventsdynatrace_openpipeline_security_events
covers configuration of OpenPipeline for Security EventsBug Fixes
dynatrace_custom_tags
resource was not deleting tags on destroydynatrace_management_zone_v2
resourcedynatrace_documents
data source panicChangelog
5861417
v1.69.02bd8b45
Updated dynatrace-configuration-as-code-core versioncb68184
Fixed #5511a101fd
Fixed #5574512d42
fixed workflow fileabccf04
Enabled OpenPipeline Resources64ae444
Credentials update for integration testsb1cf116
Chore/tidy openpipeline (#553)8869769
Fixed #549v1.68.1
Compare Source
Improvements
dynatrace_mgmz_permission
produces non-empty plans when the permissionVIEWER
isn't specified explicitly. The documentation now contains information for how to avoid thatdynatrace_aws_service
resolves conflicts between built-in and custom services now automaticallydynatrace_entities
doesn't error out anymore when the entity selector refers to a non existent management zone by name. Terraform will now print out a warning onto consoleBug Fixes
dynatrace_network_zone
was missing the ability to configure the fallback modeterraform plan
for these resourcesterraform plan
for resourcedynatrace_mgmz_permission
dynatrace_iam_policy_bindings_v2
were getting unnecessarily recreated when list of policies changesChangelog
fb5a104
v1.68.1d8bdc0a
Preliminary documentation templates for OpenPipeline9b13e11
Disabled OpenPipeline resources / data sources. Documentation not final yetfe1ce1c
Disabled Platform Bucket Integration tests until further notice3cda616
Improvement: Data Sourcedynatrace_entities
will print out a warning when the REST API produces an error while querying for entities24e3719
feat: Initial OpenPipeline resources (#546)ccd8bae
Fix: Data Sourcedynatrace_entities
doesn't error out anymore when configured with a non existent Management Zone in the Entity Selector5fbe2e2
Fixed #547445bb18
Fixed #54552c4a36
Fixed #54198514e6
removed compiler / code style warningsde961b3
Fixed #54229abc79
Fixed #54449df5fb
Resolved #540v1.68.0
Compare Source
New Resources
dynatrace_devobs_agent_optin
covers configuration for Developer Observability agent opt-indynatrace_devobs_data_masking
covers configuration for Developer Observability sensitive data maskingdynatrace_davis_copilot
covers configuration for Davis CoPilotImprovements
Bug Fixes
dynatrace_automation_workflow_aws_connections
resource forpolicy_arns
attributedynatrace_iam_permission
anddynatrace_iam_group
resourcesChangelog
fd694e5
v1.68.0df23e77
Improvements when iam_* resources return 429 codef104b2f
Fixed #53525cf388
Updated migration helper spreadsheetcdbb36f
Introduceddynatrace_davis_copilot
resourcea8a8a5a
Updateddynatrace_devobs_data_masking
with orderingd8ca2d4
Introduceddynatrace_devobs_data_masking
resource461b9f9
Fixed #534534b99e
Introduceddynatrace_devobs_agent_optin
resource01bc77a
v1.67.0aba82d3
Fixed #533a45375f
Cleaned up documentation09a4069
Introduceddynatrace_automation_workflow_aws_connections
resourcev1.67.0
Compare Source
New Resources
dynatrace_devobs_git_onprem
covers configuration for Developer Observability git on-premise servers.Improvements
DT_CLIENT_ID
andDT_CLIENT_SECRET
are now sufficient enough and are getting evaluated by all resources. For resources configuring IAM functionality theDT_ACCOUNT_ID
will be required in addition. All other environment variables (likeDYNATRACE_CLIENT_ID
,DT_IAM_CLIENT_SECRET
, ...) are nevertheless still supported.Bug Fixes
/
character for the Cluster URLDT_CLIENT_ID
,DT_CLIENT_SECRET
, ...) are now producing a helpful error message instead ofInvalid OAuth Credentials
dynatrace_entities
didn't set the attributeentities
if none are matching the specified entity selectordynatrace_hub_extension_config
just covered the first 20 extensionsSchema Updates
dynatrace_app_monitoring
got updated to be compatible with the most recent schema version of DynatraceChangelog
a70e486
Merge branch 'main' of https://github.com/dynatrace-oss/terraform-provider-dynatrace1fcf63f
Fixed #5326c07d2f
Fixed #531e2665a3
Introduceddynatrace_devobs_git_onprem
resource3760832
[Tests] Introduced first version of acceptance tests fordynatrace_golden_state
423dc0f
Enabled deletion functionality for resourcedynatrace_golden_state
11f0eaa
code cleanup8b89498
[Cleanup] Removed theunknowns
attribute from resourcedynatrace_processgroup_naming
. It serves no purpose anymore, but generates warnings when terraform logging is on debug moded2cea3a
Introduced a demo resource that can get included during tutorials2fdcdd0
Updated resource with version update only7fd9e32
Updateddynatrace_app_monitoring
resourceeeef1f2
Fixed #5299fbfa08
Fixed #528faaccb7
removed debug output57ad2ba
Fixed #5271a21e9b
Updated documentationv1.66.0
Compare Source
New Resources
dynatrace_golden_state
represents a pseudo-resource. It allows you to automatically delete settings that are not maintained by Terraform - or just get notified about them. See the documentation for details. This resource is currently not yet feature complete.Improvements
Bug Fixes
Schema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_request_attribute
dynatrace_custom_service
dynatrace_host_naming
dynatrace_processgroup_naming
dynatrace_service_naming
v1.65.0
Compare Source
New Resources
dynatrace_histogram_metrics
covers configuration for histogram data ingestiondynatrace_kubernetes_enrichment
covers configuration for generic metadata enrichment rules for KubernetesImprovements
private
attribute for thedynatrace_document
resourceBug Fixes
dynatrace_management_zone_v2
to fine tune polling mechanismv1.64.0
Compare Source
Improvements
dynatrace_platform_bucket
resourceSchema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_cloudapp_workloaddetection
dynatrace_log_timestamp
v1.63.0
Compare Source
New Data Sources
dynatrace_generic_settings
and 'dynatrace_generic_setting' cover queries for Settings 2.0 objectsdynatrace_api_tokens
anddynatrace_api_token
covers queries for access tokensv1.62.0
Compare Source
New Resources
dynatrace_web_app_custom_injection
covers configuration for web application custom injection rulesdynatrace_discovery_default_rules
covers configuration for discovery findings default rulesdynatrace_discovery_feature_flags
covers configuration for Discovery and Coverage app feature flagsBug Fixes
Schema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_attack_rules
dynatrace_vulnerability_code
dynatrace_webhook_notification
dynatrace_automation_k8s_connections
v1.61.0
Compare Source
New Resources
dynatrace_business_events_oneagent_outgoing
covers configuration for OneAgent business eventsdynatrace_oneagent_default_mode
covers configuration for OneAgent default modeBug Fixes
allowedEntities
in resourcedynatrace_credentials
terraform-provider-dynatrace -export -list-exclusions
leads to crashauto_update_chromium
ignored when set tofalse
indynatrace_synthetic_location
resourceSchema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_alerting
dynatrace_mobile_app_enablement
dynatrace_web_app_enablement
dynatrace_autotag_v2
dynatrace_automation_workflow_jira
dynatrace_automation_workflow_slack
dynatrace_disk_edge_anomaly_detectors
dynatrace_os_services
dynatrace_process_availability
v1.60.0
Compare Source
New Resources
dynatrace_network_monitor
covers configuration for network availability monitorsdynatrace_network_monitor_outage
covers configuration for network availability monitor outage handlingdynatrace_hub_permissions
covers configuration for Dynatrace Hub installation requestsdynatrace_automation_workflow_k8s_connections
covers configuration for Kubernetes Automation for Workflows appBug Fixes
dynatrace_iam_group
dynatrace_iam_user
dynatrace_iam_user
dynatrace_aws_credentials
v1.59.3
Compare Source
Bug Fixes
dynatrace_iam_group
produced non-empty plans for permissionsImprovements
dynatrace_iam*
are currently limited to 1 request per second. That rate limiter can now get configured using the environment variableDYNATRACE_IAM_RATE_LIMITER_RATE
. It defaults to 1000 (1000 milliseconds in between requests). Maximum allowed is 5000. If set to 0 or a negative value it the rate limiter is disabled.v1.59.2
Compare Source
Bug Fixes
dynatrace_network_zone
produces an update on every plandynatrace_iam*
resource can have side effect on OAuth authenticationDocumentation
v1.59.1
Compare Source
Bug Fixes
dynatrace_web_application
attributesSchema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_alerting
dynatrace_attack_settings
dynatrace_autotag_v2
dynatrace_log_sensitive_data_masking
dynatrace_log_storage
dynatrace_log_timestamp
dynatrace_management_zone_v2
dynatrace_vulnerability_settings
v1.59.0
Compare Source
New Data Sources
dynatrace_autotag
allows you to query for an Auto Tag by nameBug Fixes
dynatrace_maintenance
resulted in an error response from the REST APItype
has now been flagged asForceNew
Documentation Improvements
dynatrace_iam_*
has been improvedSchema Updates
The following resources got updated to be compatible with the most recent schema version of Dynatrace:
dynatrace_vulnerability_settings
dynatrace_attribute_allow_list
dynatrace_attack_rules
dynatrace_vulnerability_code
dynatrace_cloudapp_workloaddetection
v1.58.6
Compare Source
Bug Fixes
terraform import
could crash the Provider when an invalid / wrong ID is getting specifieddynatrace_auto_tag_v2
produced a non-empty plan when used in combination withdynatrace_autotag_rules
. The resourcedynatrace_auto_tag_v2
now offers an additional attributerules_maintained_externally
. If set totrue
the resource will ignore any changes made to its rules from outside.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.