-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Run locally the package registry during api integration tests #61699
Comments
Pinging @elastic/ingest-management (Feature:EPM) |
Just a note, we'll want to use a local registry for endpoint's functional tests too, not just API integration tests. |
@jonathan-buttner Could you point me at an example of such a functional test in/for the endpoint plugin? |
@jen-huang You are right this is not fixed |
Implemented in #69822 |
We have some api integration tests that depends on reaching package registry (https://github.com/elastic/package-registry)
So some tests could fail because we are not able to reach the package manager, and we should not rely on external services during API integration tests.
As discussed offline it's possible to run the package manager during tests. The package manager is a go application stateless, no database are required, and a docker container is already available to run it.
cc @spalger @jonathan-buttner
The text was updated successfully, but these errors were encountered: