-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[cli/dev] remove cluster module, modernize, test #84726
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
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've tested and it works great! I added a Super-NIT comment.
And I'll also re-add kibana-core
because I don't think I'm the best one here to approve it 🙂
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
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 - also tested.
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
Distributable file count
Page load bundle
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com> Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Closes #84134
Closes #84131
Closes #83976
We've had a number of issues with the dev CLI lately, detailed in the issues above, and I really want to work on some improvements like #84555, but the legacy code has been a huge mess to deal with and is a complicated bundle of evented items which are tricky to manage. This PR attempts to address all these issues at once by rewriting the dev CLI as several observable components detailed in https://github.com/spalger/kibana/blob/dev-cli/remove-cluster-usage/src/dev/cli_dev_mode/README.md.
This PR moves us to using pipes to handle the stdout from the child process now, rather than passing our stdout/stderr handles to the Kibana server. This gives us the opportunity to mask the basePathProxy target URL and should reduce the likelihood of #84131 from coming back.