-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] Re-enable registry version check #120045
Conversation
…unctional tests" This reverts commit 2fd4ec1.
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @jen-huang |
Pinging @elastic/fleet (Team:Fleet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pinging @elastic/apm-ui (Team:apm) |
@@ -13,7 +13,7 @@ import { packageRegistryPort } from './ftr_config'; | |||
import { FtrProviderContext } from './ftr_provider_context'; | |||
|
|||
export const dockerImage = | |||
'docker.elastic.co/package-registry/distribution@sha256:13d9996dd24161624784704e080f5f5b7f0ef34ff0d9259f8f05010ccae00058'; | |||
'docker.elastic.co/package-registry/distribution@sha256:de952debe048d903fc73e8a4472bb48bb95028d440cba852f21b863d47020c61'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to share this sha between fleet and apm so we won't forget to update it here next time it's bumped in fleet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opened #120235 for this
* Re-enable registry version check * Update registry image * Use dockerized registry for base x-pack api integration and functional tests * Revert "Use dockerized registry for base x-pack api integration and functional tests" This reverts commit 2fd4ec1.
@jen-huang Did you mean to backport this to 8.0? Afaict it was never backported but the labels suggests it should be. |
Summary
Resolves #117107. Put back the registry Kibana version check. The check is still skipped for
main
branch for development purposes - this is unchanged.Backport PR: #120049
^ This was done manually as the 8.0 branch is the one that would actually be impacted by this :)