Description
Repository Feature
Detections-as-Code (DaC) - (primarily custom rule management)
Problem Description
From one of our community members:
Failure to import rules with action connectors if the connector does not exist in target space. Some of our rules have actions, like Slack or PagerDuty, that rely on connectors. Connectors are exported with the rule using detection_rules kibana export-rules command. When we export the rules with connectors from Default space to repo and then deploy them from repo to Test space, then the import for rules that had actions fails ((400) Error validating create data - [actions.0.id]: expected value of type [string] but got [undefined]), but on the background the connector was created in the target space. When import is run a second time then all rules are successfully imported.
Context:
We have seen a similar issue with exception lists where the rule is attempted to import before the exception list that it references (Kibana Issue Ref #143864) and we have a workaround in the upload process.
Desired Solution
The solution would be to if this error occurs, to wait for the connector to finish being allocated and re-try uploading the rules, similarly to what we have done to address the exceptions version of this issue from elastic/kibana#143864
Considered Alternatives
No response
Additional Context
No response