[Fleet] Use new package install state machine in installCustomPackage
#189347
Assignees
Labels
Team:Fleet
Team label for Observability Data Collection Fleet team
Comments
criamico
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
criamico
changed the title
installCustomPackage
2 tasks
gergoabraham
pushed a commit
to gergoabraham/kibana
that referenced
this issue
Sep 13, 2024
…ate machine and clean up (elastic#192438) Closes elastic#189346 Closes elastic#189347 ## Summary Final PR for part I of package lifecycle improvements. - Migrate both `installPackageByUpload` and `installCustomPackage` to `installPackageWithStateMachine` and clean up the old code. As the state machine is been working in production for two releases, I am confident in using it for the custom and upload packages without a feature flag. ### Testing - Try installing a custom package - Try installing a package via upload They should work as usual ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up of #175592.
With 8.14.0 a new state machine functionality to install packages was introduced, but it was only enabled in install by registry and put under feature flag
enablePackagesStateMachine.enablePackagesStateMachineis currently enabled in production se it can be calledenablePackagesStateMachineV2The text was updated successfully, but these errors were encountered: