💚 Build Succeeded

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

🤖 GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

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

🌐 Coverage report

This pull request does not have a backport label. Could you fix it @jlind23? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@jlind23 We really need a better way to keep these things in sync for multiple repositories.

@ph agree. @levinebw what would be the best way to setup snyk on multiple repositories without having to update the config in each one individually?

@jlind23 I think robots might have existing tooling to do just that.

Snyk github action will perform the tests and then results will be pushed to the Github security tab: https://github.com/elastic/elastic-agent/security

@jlind23 are you sure we are at a stage to push the Snky scan results to a public tab?

@levinebw what would be the best way to setup snyk on multiple repositories without having to update the config in each one individually?

I don't know... @jkakavas @thomheymann @jportner may have some thoughts; and/or you can raise a question to support@snyk.io

@levinebw AFAIK code scanning alert is not publicly available, am i wrong?

@levinebw AFAIK code scanning alert is not publicly available, am i wrong?

I see some content under the public security tab about the job, https://github.com/elastic/elastic-agent/runs/6258878535?check_suite_focus=true, I suppose you are right, the results are not getting pushed publicly