[DOCS][8.x]:Update depreciation notice for index mapping updates privileges#130916
[DOCS][8.x]:Update depreciation notice for index mapping updates privileges#130916charlotte-hoblik merged 2 commits into8.19from
Conversation
charlotte-hoblik
added
>docs
|
Documentation preview: |
charlotte-hoblik
changed the title
|
Pinging @elastic/es-docs (Team:Docs) |
| the {ref}/indices-put-mapping.html[updating mapping API] or by relying on | ||
| {ref}/dynamic-mapping.html[dynamic field mapping]. In a future major release, | ||
| this privilege will not grant any mapping update permissions. | ||
| deprecated:[8.0] Starting from 8.0, this privilege no longer grants the permission |
There was a problem hiding this comment.
Could we call this a change rather than a deprecation? Or maybe a notice? Or something like a partial deprecation? Do we have a clear nomenclature for what such a thing should be called?
My point is that the "deprecated" term tends to push people away from the feature, rather than bringing attention to what exactly changed.
There was a problem hiding this comment.
Thanks for the feedback! I used deprecated:[8.0] just for the visual effect, since the syntax doesn’t support alternatives like change. I used an important block instead in the 9.x PR, and added the same here. Let me know what you think!
I went with IMPORTANT admonition because it felt like the clearest fit, but if you think NOTE would be more appropriate, happy to switch.
Here’s the list of supported admonitions and when to use them: https://elastic.github.io/docs-builder/syntax/admonitions/
…ileges (#130916) * Update index mapping update privileges * Remove `depricated` tag
…ileges (#130916) * Update index mapping update privileges * Remove `depricated` tag
3 participants
This PR updates the depreciation notice for 4 write-related operations on indices: (8.x asciidoc version)
createcreate_docindexwriteBased on: elastic/docs-content#1668
9.x Version: #130894