global artifacts manifest_type

[intxgo]

Change Summary

Global artifacts are rolled out gradually, only a selected few endpoints receive candidate artifacts to verify them before the rollout will progress. This PR adds global artifacts manifest type field to indicate which artifacts manifest type was currently used by the Endpoint.

Sample values

Endpoint using standard stable artifacts:
"Endpoint.policy.applied.artifacts.global.manifest_type": "stable"

Endpoint testing candidate artifacts:
"Endpoint.policy.applied.artifacts.global.manifest_type": "candidate"

Sample document:

Endpoint altert and Endpoint policy response:

{
    "Endpoint": {
        "policy": {
            "applied": {
                "artifacts": {
                    "global": {
                        "manifest_type": "stable",
                    },
}

Release Target

Q/A

For mapping changes:

• I ran make after making the schema changes, and committed all changes
• If these field(s) are "exception"-able, I made a companion PR to Kibana adding it (see Readme)
• If this is a metadata change, I also updated both transform destination schemas to match

For Transform changes:

• The new transform successfully starts in Kibana
• The corresponding transform destination schema was updated if necessary

[intxgo]

it looks like some of the the custom documentation was modified manually, so the update script moved things around when sorting the updated filed

⚠️ custom documentation should be updated by script ideally (on Linux, as it's the only supported system for running make in endpoint-package repository). Updating it manually is not an error, but it leads to unexpected changes on other's PRs, such as unsorted fields