Add update-spec updatecli workflow

[reakaleek]

What does this pull request do?

Moves the update specs workflow from apm-server to the consumer using updatecli to have a "dependabot"-like experience.

How to test

GITHUB_TOKEN=<token>\
GIT_USER=<username> \
GIT_EMAIL=j<email> \
updatecli diff -c .ci/update-specs.yml

Related issues

• https://github.com/elastic/observability-robots/issues/1516

[apmmachine]

💚 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-02-09T08:24:28.967+0000

• Duration: 22 min 50 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.

• run module tests for <modules> : Run TAV tests for one or more modules, where <modules> can be either a comma separated list of modules (e.g. memcached,redis) or the string literal ALL to test all modules

• run benchmark tests : Run the benchmark test only.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[trentm]

1. Should this PR also handle removing the now obsolete (I think) https://github.com/elastic/apm-agent-nodejs/blob/main/test/integration/api-schema/apm-server-schema/log.json file? It was removed from apm-server.git (where these spec files used to be sync'd from) in Add ECS log files to the intake log endpoint apm-server#9349

2. I guess updatecli doesn't support mapping a full directory or a glob pattern?

[reakaleek]

1. Should this PR also handle removing the now obsolete (I think) https://github.com/elastic/apm-agent-nodejs/blob/main/test/integration/api-schema/apm-server-schema/log.json file? It was removed from apm-server.git (where these spec files used to be sync'd from) in elastic/apm-server#9349
2. I guess updatecli doesn't support mapping a full directory or a glob pattern?

1. Since, the log.json file is also not part of https://github.com/elastic/apm-data/tree/main/input/elasticapm/docs/spec/v2, I guess it's safe to remove it. Will do that in this PR.

2. Yes, unfortunately there is no native way to sync/manipulate multiple files at once. We concluded, that having hardcoded list is feasible in this case because the amount of files rarely changes.

Update:

3f85aa3

[reakaleek]

@trentm

FYI, there is an issue to bundle the schemas into one file.

elastic/apm-data#15

Hence, the mentioned issues will be solved there.