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
We changed all our existing CWS terraform resources to reflect the change of the API endpoint in Datadog, and the expectation was that the plan will not fail, but will run normally.
Actual Behavior
The terraform plan is failing and the apply cannot be executed. Error: error fetching cloud workload security agent rule from /api/v2/security_monitoring/cloud_workload_security/agent_rules/xxx-xr-xsw: 403 Forbidden: {"errors":["You can't query this Cloud Workload Security endpoint anymore. It has been migrated to corresponding CSM Threats endpoint. See the API documentation for reference: https://docs.datadoghq.com/api/latest/cloud-workload-security/"]}
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Datadog Terraform Provider Version
v3.39.0
Terraform Version
v1.3.9
What resources or data sources are affected?
datadog_csm_threats_agent_rule
Terraform Configuration Files
Relevant debug or panic output
No response
Expected Behavior
We changed all our existing CWS terraform resources to reflect the change of the API endpoint in Datadog, and the expectation was that the plan will not fail, but will run normally.
Actual Behavior
The terraform plan is failing and the apply cannot be executed.
Error: error fetching cloud workload security agent rule from /api/v2/security_monitoring/cloud_workload_security/agent_rules/xxx-xr-xsw: 403 Forbidden: {"errors":["You can't query this Cloud Workload Security endpoint anymore. It has been migrated to corresponding CSM Threats endpoint. See the API documentation for reference: https://docs.datadoghq.com/api/latest/cloud-workload-security/"]}
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: