-
Notifications
You must be signed in to change notification settings - Fork 123
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
Add server:capabilities api action #2242
Conversation
Codecov Report
@@ Coverage Diff @@
## 2-dev #2242 +/- ##
==========================================
- Coverage 92.47% 92.34% -0.13%
==========================================
Files 124 124
Lines 8190 8234 +44
==========================================
+ Hits 7574 7604 +30
- Misses 616 630 +14
Continue to review full report at Codecov.
|
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.
Apply requested changes and this will be good to me
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.
Missing functional tests
this._info.elasticsearch = await global.kuzzle.ask('core:storage:public:info:get'); | ||
this._info.redis = await global.kuzzle.ask('core:cache:public:info:get'); |
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.
Those promise should be made in //
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What does this PR do ?
Exposing specific properties to the configuration because
server:getConfig
/server:info
give too much info. We want a less verbose API action.With the following information:
How should this be manually tested?
Start Kuzzle with
docker-compose up
, then with kourou use the capabilities action:kourou server:capabilities
or send GET request to the routehttp:localhost:7512/_capabilities
route.