-
Notifications
You must be signed in to change notification settings - Fork 73
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
Spec for the new Query Role API #2676
Conversation
@@ -52,6 +52,7 @@ export class RoleDescriptor { | |||
* @doc_id run-as-privilege | |||
*/ | |||
run_as?: string[] | |||
description?: string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not related to the new API.
Role Descriptors have a description field since elastic/elasticsearch#107088 .
|
||
/** | ||
* Retrieves roles in a paginated manner. You can optionally filter the results with a query. | ||
* @rest_spec_name security.query_role |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note this is singular here query_role
, but the specs dir is plural (query_roles
).
ES endpoints are singular, eg https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-query-api-key.html , but I see it in the specs that the dir is named query_api_keys
.
* under the License. | ||
*/ | ||
|
||
import { RoleAggregationContainer } from './types' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this import should be RoleQueryContainer right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch!
|
Thanks @l-trotta . I've addressed your review. Please take another look. |
following what the validator is saying, |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
we're missing the |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.15 8.15
# Navigate to the new working tree
cd .worktrees/backport-8.15
# Create a new branch
git switch --create backport-2676-to-8.15
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e021a35cc234a48828c43e61621ad2c6e99ea625
# Push it to GitHub
git push --set-upstream origin backport-2676-to-8.15
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.15 Then, create a pull request where the |
Thank you for your help on this @l-trotta ! Much appreciated. |
The rest specs for the new query role API in 8.15 elastic/elasticsearch#108733 .
The docs for it are at elastic/elasticsearch#110473 .