[Cloud Security] Mark internal cloud_security_posture ingest pipelines as managed

[zk2k2]

Summary

Fixes:

• [Bug] [Cloud Security] Internal pipelines of cloud security are not marked as managed #226696

This PR fixes a bug where internal ingest pipelines used by the cloud_security_posture plugin were not marked as managed.
By adding the _meta.managed: true field to these pipelines, they will now be correctly recognized as managed pipelines by Elasticsearch and Kibana.

This prevents accidental user modifications and aligns with other Elastic-managed pipelines.

---

Checklist

• Follows EUI writing guidelines and includes i18n support where applicable
• Documentation updated as needed
• Unit or functional tests updated or added
• Checked for breaking HTTP API changes
• Flaky Test Runner used on tests changed
• Release Notes section included and appropriate label applied

---

Identify risks

This change only adds metadata to existing ingest pipeline definitions and does not affect pipeline logic or data processing.
Risk of regressions or data loss is minimal. The change improves system stability by marking pipelines as managed.

---

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
bddde25

Please, read and sign the above mentioned agreement if you want to contribute to this project

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

[opauloh]

cc @CohenIdo can you review it?

[zk2k2]

Just commenting so that the CLA checks works

[opauloh]

/ci

[opauloh]

@elasticmachine run docs-build

[CohenIdo]

LGTM

[maxcold]

@zk2k2 I think you need to actually online sign the CA agreement so we could merge

[opauloh]

/ci

[zk2k2]

@maxcold I signed the CLA multiple times I don't know why it's not picking up on it

[maxcold]

@zk2k2 weird, haven't had a case like that before. Did you use the same email zied.kharrat@insat.ucar as you used for the commit authoring?

[opauloh]

/ci

[maxcold]

@elasticmachine run docs-build

[opauloh]

/ci

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 08877b6

Metrics [docs]

✅ unchanged

History

• 💔 Build #323078 failed 9c4fddf
• 💔 Build #322944 failed bddde25

[maxcold]

@zk2k2 sorry for the ping but we would like to merge this PR and can't without CLA check passing. Can you check if you signed the agreement with the same email you did commits? It's zied.kharrat@insat.ucar . If you did indeed sign with the same email, I will bring it up internally with relevant team

[zk2k2]

Hi @maxcold , I am pretty sure I signed the CLA with the following email zied.kharrat@insat.ucar.tn, I also tried signing it with my other GitHub emails. If this helps, I have successfully signed the CLA for another PR to another issue #227619, pretty sure it was using zied.kharrat@insat.ucar.tn, let me know if I can help any other way

[maxcold]

@zk2k2 yeah, I think the issue is that the commit was created with email zied.kharrat@insat.ucar which is missing .tn in the end. You can see that in the list of commits, your user is not being linked properly to the commit (there is no link to https://github.com/zk2k2) .

Anyway, the simplest way to fix it, I think, is to recreate this PR, making sure the commit is made with email zied.kharrat@insat.ucar.tn, and then you should be able to sign CLA
Another option is to try to change the commit in this branch and amend the email, but it might get messy
Or if you don't want to spend time on that, I can recreate the PR from my name with your change, but I don't want to steal your thunder :)

[zk2k2]

@maxcold Oh I see, my bad! I will recreate the PR ASAP :) thanks for pointing it out!

[zk2k2]

HI @maxcold, i've submitted a new PR #230106 and CLA check works this time, thanks for your patience and help :)!

[maxcold]

@zk2k2 thanks! closing this PR then