-
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] Fix branch conditions to check against main
and add skip version check config option
#116530
Conversation
Pinging @elastic/fleet (Team:Fleet) |
@elasticmachine merge upstream |
Taking over this PR to fix Kibana CI due issue with EPR on 8.0.0 |
Thanks @joshdover! |
@@ -57,8 +57,8 @@ export const createAppContextStartContractMock = (): MockedFleetAppContext => { | |||
agentIdVerificationEnabled: true, | |||
}, | |||
config$, | |||
kibanaVersion: '8.0.0', | |||
kibanaBranch: 'master', | |||
kibanaVersion: '8.99.0', // Fake version :) |
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.
At least until ~2030 ;-)
main
main
and add skip version check config option
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
History
To update your PR or re-run it, just comment with: |
…rsion check config option (elastic#116530)
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Summary
This PR updates some conditions in Fleet which check against the branch name. Do not merge until default branch in this repo has been renamed to
main
as well.This also adds the config option
xpack.fleet.developer.disableRegistryVersionCheck
that enables bypassing of Kibana version constraints on requests to EPR. This is currentlytrue
by default until 8.0 packages are published and tests which depend on those packages are able to pass without bypassing version check (#102283, #102282, #116522).