-
Notifications
You must be signed in to change notification settings - Fork 128
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
chore(release): backport master to beta #2596
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR adds a new _ready route, that allow orchestrators that uses probes to detect if the Kuzzle server is ready to accept incoming requests (node started, up and running and not overloaded) This specific implementation allow this route to not be part of the right system of Kuzzle. So that orchestrator can use this route to detect if Kuzzle is alive.
fix: update es version to avoid anyController error
* feat: collection getSettings * chore: lint * test: fix the test * Update doc/2/api/controllers/collection/get-settings/index.md * fix: getSettings redundant code --------- Co-authored-by: Eric <[email protected]>
…perty fix: started property from backend should be accessible onto plugins
release: 2-dev to master
## [2.41.0](v2.40.1...v2.41.0) (2025-03-05) ### Features * add a new unauthenticated `/_ready` HTTP endpoint ([#2592](#2592)) ([52d54fa](52d54fa)) * collection getSettings ([#2588](#2588)) ([da75cbc](da75cbc)) ### Bug Fixes * add a getter for started property and a setter, create _started private property ([aacee11](aacee11)) * update es version to avoid anyController error ([6d594dd](6d594dd))
|
🎉 This PR is included in version 2.42.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.42.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do ?
How should this be manually tested?
Other changes
Boyscout