[Dataset quality] configuring dockerized package registry in tests#234891
[Dataset quality] configuring dockerized package registry in tests#234891yngrdyn wants to merge 15 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
mohamedhamed-ahmed
left a comment
There was a problem hiding this comment.
LGTM! Great job spotting this 🤞 hope this makes our tests less flaky
jennypavlova
left a comment
There was a problem hiding this comment.
LGTM 🚀 Thank you for fixing that!
| const bitbucketDatasetName = 'atlassian_bitbucket.audit'; | ||
| const bitbucketAuditDataStreamName = `logs-${bitbucketDatasetName}-${defaultNamespace}`; | ||
| const bitbucketPkg = { | ||
| name: 'atlassian_bitbucket', |
There was a problem hiding this comment.
atlassian_bitbucket is not part of distribution:lite docker
| `--server.publicBaseUrl=${kbnUrl}`, | ||
| // Allow dynamic config overrides in tests | ||
| `--coreApp.allowDynamicConfigOverrides=true`, | ||
| ...(dockerRegistryPort |
There was a problem hiding this comment.
@dmlemeshko this configuration was not set before the changes so I'm not sure the docker was being used
Do you know if that was the case?
And I believe that's why all scout tests are failing.
Does scout needs this configuration to query the local package registry?
| `--permissionsPolicy.report_to=${JSON.stringify(['violations-endpoint'])}`, | ||
| // Allow dynamic config overrides in tests | ||
| `--coreApp.allowDynamicConfigOverrides=true`, | ||
| ...(dockerRegistryPort |
…age-registry-in-tests
|
closing this and opening a new PR to carry on the work there as this is already too old to fix the conflicts. [Dataset quality] configuring dockerized package registry in tests |
…250040) ## Summary We have been dealing with a lot of flakiness in our tests due to package registry not being available, this PR changes the package registery being used to the dockerized one in Dataset Quality. As well as centralizing its usage in kbn-test package so that it can later on be used from a central place by other teams instead of duplicating it in every test suite. This is work continuation for [[Dataset quality] configuring dockerized package registry in tests](#234891).
…lastic#250040) ## Summary We have been dealing with a lot of flakiness in our tests due to package registry not being available, this PR changes the package registery being used to the dockerized one in Dataset Quality. As well as centralizing its usage in kbn-test package so that it can later on be used from a central place by other teams instead of duplicating it in every test suite. This is work continuation for [[Dataset quality] configuring dockerized package registry in tests](elastic#234891). (cherry picked from commit 8902479)
…lastic#250040) ## Summary We have been dealing with a lot of flakiness in our tests due to package registry not being available, this PR changes the package registery being used to the dockerized one in Dataset Quality. As well as centralizing its usage in kbn-test package so that it can later on be used from a central place by other teams instead of duplicating it in every test suite. This is work continuation for [[Dataset quality] configuring dockerized package registry in tests](elastic#234891). (cherry picked from commit 8902479)
…lastic#250040) ## Summary We have been dealing with a lot of flakiness in our tests due to package registry not being available, this PR changes the package registery being used to the dockerized one in Dataset Quality. As well as centralizing its usage in kbn-test package so that it can later on be used from a central place by other teams instead of duplicating it in every test suite. This is work continuation for [[Dataset quality] configuring dockerized package registry in tests](elastic#234891). (cherry picked from commit 8902479) # Conflicts: # x-pack/platform/test/api_integration_deployment_agnostic/default_configs/feature_flag.serverless.config.base.ts # x-pack/platform/test/api_integration_deployment_agnostic/default_configs/serverless.config.base.ts # x-pack/solutions/observability/test/functional/config.base.ts
…lastic#250040) ## Summary We have been dealing with a lot of flakiness in our tests due to package registry not being available, this PR changes the package registery being used to the dockerized one in Dataset Quality. As well as centralizing its usage in kbn-test package so that it can later on be used from a central place by other teams instead of duplicating it in every test suite. This is work continuation for [[Dataset quality] configuring dockerized package registry in tests](elastic#234891). (cherry picked from commit 8902479) # Conflicts: # x-pack/platform/test/api_integration_deployment_agnostic/default_configs/feature_flag.serverless.config.base.ts # x-pack/platform/test/api_integration_deployment_agnostic/default_configs/serverless.config.base.ts # x-pack/solutions/observability/test/functional/config.base.ts
Closes #233620, #234087, #235057, #235275, #235633, #235723
We have been dealing with a lot of flakiness in our tests due to package registry not being available, after checking the configs I discovered we are not using the dockerized package registry, we are only using it in our api tests (which seems to be more stable).
This PR aims to use dockerized package registry for all our tests.
As a stretch goal of this PR, I agreed with @dmlemeshko to centralize the package-registry config into
@kbn/testsince was duplicated all over the place and it also benefit other teams, special configuration can be still added insidedefineDockerServersConfigand overriden for special cases