Mark user profile APIs as public #133819
Merged
Mark user profile APIs as public #133819
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
They are used in Kibana, and documented as Kibana-only in the documentation.
pquentin
added
>non-issue
auto-backport
|
Pinging @elastic/es-security (Team:Security) |
|
Serverless availability is encoded in the Elasticsearch specification: https://github.com/elastic/elasticsearch-specification/blob/424b5471c7acdc4e4f088ed186fe7ce97db23c2b/specification/security/activate_user_profile/Request.ts#L40. rest-api-spec is only about the stack. |
pquentin
added a commit
to pquentin/elasticsearch
that referenced
this pull request
Sep 5, 2025
They are used in Kibana, and documented as Kibana-only in the documentation.
pquentin
added a commit
to pquentin/elasticsearch
that referenced
this pull request
Sep 5, 2025
They are used in Kibana, and documented as Kibana-only in the documentation.
pquentin
added a commit
to pquentin/elasticsearch
that referenced
this pull request
Sep 5, 2025
They are used in Kibana, and documented as Kibana-only in the documentation.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 5, 2025
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 5, 2025
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 5, 2025
sarog
pushed a commit
to portsbuild/elasticsearch
that referenced
this pull request
Sep 11, 2025
They are used in Kibana, and documented as Kibana-only in the documentation.
sarog
pushed a commit
to portsbuild/elasticsearch
that referenced
this pull request
Sep 19, 2025
They are used in Kibana, and documented as Kibana-only in the documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
They are used in Kibana through the JS client, and documented as Kibana-only in the docs, so the correct marker is in fact "public".
I'm planning to generate the rest-api-spec from the Elasticsearch specification, but I need to eliminate the differences first.