@elasticmachine merge upstream

@dplumlee Should these types also be updated to reflect that techniques are optional?
https://github.com/elastic/kibana/blob/master/x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/types.ts#L216

Also is there a way to combine those types with the ones defined here? Or is there a reason they need to be duplicated?
https://github.com/elastic/kibana/blob/master/x-pack/plugins/security_solution/common/detection_engine/schemas/common/schemas.ts#L448

@peluja1012 there's no reason they need to be duplicated, I'll consolidate them. As for the technique field being optional, as it stands right now, all rules created and have a technique array and the form to create rules, defaults every threat to an empty array. I talked to @marshallmain and we concurred that the best way to handle switching to an optional field was to leave the schema as is and change the form validation to allow empty arrays

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 468f9bc

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

Distributable file count

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

History

• 💚 Build #94134 succeeded d48c696
• 💔 Build #94130 failed e67273ab8087afd4c0b93d479dcdfe62d7410371
• 💚 Build #93298 succeeded 46e446d2e5f73a866576e9f8357a86b3f015d2fc
• 💔 Build #93290 failed c2d8900800e0e979a439b5c3f1565b6437e1ec93

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream