[Uptime] Index Status API to Rest#59657
Conversation
|
Pinging @elastic/uptime (Team:uptime) |
justinkambic
left a comment
There was a problem hiding this comment.
This looks really good to me, had one comment that we maybe should chat about offline.
| */ | ||
|
|
||
| export enum REST_API_URLS { | ||
| INDEX_STATUS = '/api/uptime/index_status', |
There was a problem hiding this comment.
Is the thinking that we will add all the URL paths here as we touch them? If so it might be good to add a follow-up issue for this so to jumpstart adoption.
There was a problem hiding this comment.
| if (!response.ok) { | ||
| throw new Error(response.statusText); | ||
| } | ||
| const responseData = await response.json(); |
There was a problem hiding this comment.
We keep adding such similar boilerplate for making fetch requests, I think we could really abstract a lot of this code away with a generic function.
There was a problem hiding this comment.
also done in https://github.com/elastic/kibana/pull/59881/files
| export function* fetchIndexStatusEffect() { | ||
| yield takeLatest( | ||
| indexStatusAction.get, | ||
| fetchEffectFactory(fetchIndexStatus, indexStatusAction.success, indexStatusAction.fail) |
There was a problem hiding this comment.
fetchEffectFactory(fetchIndexStatus, indexStatusAction.success, indexStatusAction.fail)I like this get, success, fail pattern.
There was a problem hiding this comment.
yes, it really makes usage simple.
| }, | ||
| }); | ||
| } catch (e) { | ||
| return response.internalError({ body: { message: e.message } }); |
There was a problem hiding this comment.
@andrewvc has expressed reservations about returning descriptive error messages, this might be something we want to discuss here.
There was a problem hiding this comment.
i am not sure what do you mean by that?
There was a problem hiding this comment.
@andrewvc would you have any issue with returning this message? I thought I remembered you expressing concern about security implications of exposing error messages in API responses.
|
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* master: [Step 1][App Arch] Saved object migrations from kibana plugin to new platform (elastic#59044) adds new test (elastic#60064) [Uptime] Index Status API to Rest (elastic#59657)
* master: (40 commits) skips 'config_open.ts' files from linter check (elastic#60248) [Searchprofiler] Spacing between rendered shards (elastic#60238) Add UiSettings validation & Kibana default route redirection (elastic#59694) [SIEM][CASE] Change configuration button (elastic#60229) [Step 1][App Arch] Saved object migrations from kibana plugin to new platform (elastic#59044) adds new test (elastic#60064) [Uptime] Index Status API to Rest (elastic#59657) [SIEM] Adds 'Closes and opens signals' Cypress test (elastic#59950) [NP] Graph migration (elastic#59409) [ML] Clone analytics job (elastic#59791) Move VALUE_CLICK_TRIGGER and APPLY_FILTER_TRIGGER to ui_action… (elastic#60202) Handle improperly defined Watcher Logging Action text parameter. (elastic#60169) Move select range trigger to uiActions (elastic#60168) [SIEM][CASES] Configure cases: Final (elastic#59358) Closes elastic#59784. Sets xpack.apm.serviceMapEnabled default value true. (elastic#60153) [siem/cypress] update junit filename to be picked up by runbld (elastic#60156) OSS logic added to test environment (elastic#60134) Move canvas setup into app mount (elastic#59926) enable triggers_actions_ui plugin by default (elastic#60137) Expose Elasticsearch from start and deprecate from setup (elastic#59886) ...
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
* gql to rest * update snap * fix api Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
As part of #58020
Convert Index Status API from GQL to rest !!