[Security] Reducing the metadata name of the pipelines to less than 63 chars

[dkirchan]

Backstage has a limitation of 63 chars in order to allow the resource entities to be created. Otherwise they are silently skipped.

The RREs created can be validated against: https://backstage.elastic.dev/entity-validation

This PR addresses the required name change for the pipelines to be created.

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[delanni]

@nuugen suggested that we do the kibana-buildkite prefix as a good practice, but it's true it's quite long/bloaty. Is there a legible alternative if we keep the kibana-buildkite, if not, I'm okay with kb-, we encode the categories in other fields anyway. @nuugen what do you think?

[dkirchan]

kibana-buildkite with the rule of 36 chars makes the definition quite difficult.

We can either keep kb and the pipeline name as a convention OR `kibana-{abbreviation of team/org and scope}-{name}

Such as kibana-serverless-ssqg-detection-engine

What would you prefer?