Transform schema v2

[pzl]

Change Summary

Updated the transform definitions to match the new Transform Spec

this involved mostly renaming files and translating from json to yaml

I tested these package changes against this PR: elastic/kibana#140046

You can see that the new transforms are installed below.

I added an Endpoint to make sure the data was still making it's way to the Endpoint list.

Release Target

next

Q/A

For mapping changes:

• I ran make after making the schema changes, and committed all changes
• 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

Upgrade (from current json-based transform) & downgrade operate successfully

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-08-03T21:13:20.261+0000

• Duration: 7 min 26 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[pzl]

It appears that Fleet may not yet support installing packages following the new spec.

Here is the fleet issue tracker for that support: elastic/kibana#134321

[kevinlog]

@joeypoon @pzl

I resolved the conflicts in this file by updating go.mod and go.sum in addition to adding the new mappings to the united index.

Let me know if it looks OK to you. I tested installing the package with this change with this PR: elastic/kibana#140046. We can merge if everything goes in on the Fleet side.

[pzl]

@kevinlog looks good, verified the two extra fields (last_checkin_message, components) from Joey's united change are in here. The resulting diff looks correct. I can't self-approve my PR, but all looks good here.

will keep holding until kibana PR gets merged

[kevinlog]

/test

[kevinlog]

@pzl

looks good! Can you just confirm that you stood this up and it installed correctly in a locally running stack?

[pzl]

@kevinlog

Yes, This worked correctly in a local stack. Tested three scenarios:

• fresh install (no bundled endpoint package in kibana, installed this fresh). ✔️
• upgrade (started with package from main branch, installed, checked that transforms for main (json-style-v1) were running. Then restarted my local EPR to include the new build and kibana upgraded endpoint package (played with manifest version locally to make sure it picked it up) and checked that old transforms were stopped, removed, and the new yml-style-v2 were the ones now running ✔️
• downgrade put some intentional errors in the package so it downgraded to previous json ones ✔️

[kevinlog]

LGTM!

[elasticmachine]

Package endpoint - 8.10.0 containing this change is available at https://epr.elastic.co/search?package=endpoint