[DOCS] Move EQL APIs to separate page #74846
Merged
Conversation
This file contains hidden or 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
Contributor
Author
|
@elasticmachine ok to test |
jrodewig
added
v7.13.4
v7.14.1
v7.15.0
:Analytics/EQL
elasticmachine
added
Team:QL (Deprecated)
Collaborator
|
Pinging @elastic/es-ql (Team:QL) |
Collaborator
|
Pinging @elastic/es-docs (Team:Docs) |
lockewritesdocs
approved these changes
Jul 1, 2021
Contributor
lockewritesdocs
left a comment
lockewritesdocs
left a comment
There was a problem hiding this comment.
+1 @jrodewig -- left a small nit if you want to incorporate.
This was referenced Jul 1, 2021
jrodewig
added a commit
that referenced
this pull request
Jul 1, 2021
In preparation for #74845, we need to create formal API reference documentation for our SQL APIs. Due to the number of SQL APIs, we'll likely need to create a separate nested page for them. For parity, this PR moves our EQL APIs to a separate page as well. Previously, they were listed under our search APIs.
jrodewig
added a commit
that referenced
this pull request
Jul 1, 2021
In preparation for #74845, we need to create formal API reference documentation for our SQL APIs. Due to the number of SQL APIs, we'll likely need to create a separate nested page for them. For parity, this PR moves our EQL APIs to a separate page as well. Previously, they were listed under our search APIs.
jrodewig
added a commit
that referenced
this pull request
Jul 1, 2021
In preparation for #74845, we need to create formal API reference documentation for our SQL APIs. Due to the number of SQL APIs, we'll likely need to create a separate nested page for them. For parity, this PR moves our EQL APIs to a separate page as well. Previously, they were listed under our search APIs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
In preparation for #74845, we need to create formal API reference documentation for our SQL APIs.
Due to the number of SQL APIs, we'll likely need to create a separate nested page for them. For parity, this PR moves
our EQL APIs to a separate page as well. Previously, they were listed under our search APIs.