Skip to content
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

[Security Solution][DQD][API] update results API to use path params in place of query params #183696

Merged
merged 2 commits into from
May 17, 2024

Conversation

kapral18
Copy link
Contributor

  • Changed the RESULTS_API_ROUTE to RESULTS_INDICES_LATEST_ROUTE with path parameter {pattern}.
  • Updated getStorageResults function to use the new route.
  • Modified tests to reflect the new route and parameter usage.
  • Updated server route validation to use path parameters instead of query parameters.

closes #182868

This is an internal route api change, so no breaking changes

Before
image

After:
image

@kapral18 kapral18 added release_note:skip Skip the PR/issue when compiling release notes backport:skip This commit does not require backporting Team:Threat Hunting Security Solution Threat Hunting Team Team:Threat Hunting:Explore v8.15.0 labels May 17, 2024
@kapral18 kapral18 self-assigned this May 17, 2024
@kapral18 kapral18 requested a review from a team as a code owner May 17, 2024 06:36
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore)

Copy link
Contributor

@semd semd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

kapral18 added 2 commits May 17, 2024 13:16
…nstead of query params

- Changed the `RESULTS_API_ROUTE` to `RESULTS_INDICES_LATEST_ROUTE` with path parameter `{pattern}`.
- Updated `getStorageResults` function to use the new route.
- Modified tests to reflect the new route and parameter usage.
- Updated server route validation to use path parameters instead of query parameters.

closes elastic#182868
@kapral18 kapral18 force-pushed the feat/182868-change-get-results-api branch from 8c38f94 to 9f9c5fa Compare May 17, 2024 11:38
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 15.1MB 15.1MB +76.0B

History

  • 💔 Build #210629 failed 8c38f941b8c2b684eef71512f257ee6e410936f5

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @kapral18

@kapral18 kapral18 merged commit 3c4b33b into elastic:main May 17, 2024
34 checks passed
@kapral18 kapral18 deleted the feat/182868-change-get-results-api branch May 17, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Threat Hunting:Explore Team:Threat Hunting Security Solution Threat Hunting Team v8.15.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Security Solution][DQD][API] Change /results route to support new api design (Phase 1)
4 participants