[DOCS] Minor fixes in transform documentation #51633
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
lcawl
added
>docs
|
Pinging @elastic/ml-core (:ml/Transform) |
|
Pinging @elastic/es-docs (>docs) |
lcawl
changed the title
lcawl
added a commit
that referenced
this pull request
Jan 30, 2020
lcawl
added a commit
that referenced
this pull request
Jan 30, 2020
lcawl
added a commit
that referenced
this pull request
Jan 30, 2020
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.
This PR adds the missing deprecation indicators (https://github.com/elastic/docs#additions-and-deprecations) for the data_frame_transform_admin and data_frame_transform_user roles (
https://www.elastic.co/guide/en/elasticsearch/reference/master/built-in-roles.html). It also sorts the list so that the new transform_admin and transform_user are in the right place alphabetically.
It also updates the eCommerce tutorial (https://www.elastic.co/guide/en/elasticsearch/reference/master/ecommerce-transforms.html) such that the API examples are collapsed by default. The steps can all be done in Kibana, which is why it's optional to view the API details.
Preview: