generated from hashicorp/terraform-provider-scaffolding-framework
-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Labels
Description
Example
resource "crowdstrike_it_automation_task" "osquery_example" {
name = "OSQuery Example"
access_type = "Shared"
description = "Example task using OSQuery"
type = "query"
os_query = "SELECT name, version FROM programs WHERE name LIKE '%chrome%';"
assigned_user_ids = [
"valid-id"
]
}│ Error: Error updating IT automation task
│
│ with crowdstrike_it_automation_task.script_content_example,
│ on resource.tf line 13, in resource "crowdstrike_it_automation_task" "script_content_example":
│ 13: resource "crowdstrike_it_automation_task" "script_content_example" {
│
│ Could not update task, error: [PATCH /it-automation/entities/tasks/v1][400] iTAutomationUpdateTaskBadRequest
│ &{Errors:[{Code:400 Message:user IDs not found:<id>}] Meta:PoweredBy:falconforitapi
│ QueryTime:0.020122681 TraceID:79d9a70abd334be9b1bd3a73d0b743f7}}Returning 400 for a user that exists, but lacks permissions is confusing. The api should distinguish between invalid id's and a user that lacks permissions.