Skip to content
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

Specify security.get_role_mapping name as list #53207

Merged
merged 3 commits into from
May 27, 2020
Merged

Conversation

russcam
Copy link
Contributor

@russcam russcam commented Mar 6, 2020

This commit updates the rest API spec for
security.get_role_mapping to specify name as a list type.
Multiple values can be specified for name as a comma-separated list.

This commit updates the rest API spec for
security.get_role_mapping to specify name as a list type.
Multiple values can be specified for name as a comma-separated list.
@tvernum tvernum added the :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) label Mar 6, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (:Security/Authentication)

@rjernst rjernst added the Team:Security Meta label for security team label May 4, 2020
@colings86
Copy link
Contributor

@russcam are you still wanting to progress this PR or should it be closed?

@russcam
Copy link
Contributor Author

russcam commented May 21, 2020

Yes I am @colings86. If it LGTY , I can merge it in and backport

@colings86
Copy link
Contributor

colings86 commented May 21, 2020

@elastic/es-security could someone take this and work with @russcam to get it merged by reviewing the change?

@jkakavas jkakavas self-assigned this May 21, 2020
@jkakavas
Copy link
Member

jkakavas commented May 21, 2020

@russcam apologies that this fell through the cracks. Do you mind tackling the security.get_role as well in this one so that we have consistency over all the security API specs ?

@russcam
Copy link
Contributor Author

russcam commented May 25, 2020

no worries @jkakavas , I'll update security.get_role too

This commit updates the REST API spec for
security.get_role to specify name as a list type.
@jkakavas
Copy link
Member

@elasticmachine update branch

Copy link
Member

@jkakavas jkakavas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@russcam russcam merged commit fc521ef into master May 27, 2020
@russcam russcam deleted the russcam-patch-23 branch May 27, 2020 02:23
@ezimuel
Copy link
Contributor

ezimuel commented Oct 15, 2020

I just discovered that this PR has not been backported to 7.x and 7.10 branches. This affects the generation of the clients, since we use the API spec.
/cc @elastic/clients-team

ezimuel pushed a commit to ezimuel/elasticsearch that referenced this pull request Oct 16, 2020
…lastic#53207)

This commit updates the rest API specs for

- security.get_role_mapping to specify name as a list type.
- security.get_role to specify name as a list type.
ezimuel added a commit that referenced this pull request Oct 16, 2020
…53207) (#63786)

This commit updates the rest API specs for

- security.get_role_mapping to specify name as a list type.
- security.get_role to specify name as a list type.

Co-authored-by: Russ Cam <[email protected]>
ezimuel added a commit that referenced this pull request Oct 16, 2020
…53207) (#63785)

This commit updates the rest API specs for

- security.get_role_mapping to specify name as a list type.
- security.get_role to specify name as a list type.

Co-authored-by: Russ Cam <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants