elasticsearch-api 8.18.0 → 9.0.1

data/lib/elasticsearch/api/actions/security/get_user_privileges.rb

@@ -15,18 +15,25 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Retrieves security privileges for the logged in user.
+        # Get user privileges.
+        # Get the security privileges for the logged in user.
+        # All users can use this API, but only to determine their own privileges.
+        # To check the privileges of other users, you must use the run as feature.
+        # To check whether a user has a specific list of privileges, use the has privileges API.
         #
+        # @option arguments [String] :application The name of the application. Application privileges are always associated with exactly one application. If you do not specify this parameter, the API returns information about all privileges for all applications.
+        # @option arguments [String] :priviledge The name of the privilege. If you do not specify this parameter, the API returns information about all privileges for the requested application.
+        # @option arguments [Name, Null] :username [TODO]
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-get-user-privileges.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-get-user-privileges
         #
         def get_user_privileges(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.get_user_privileges' }
@@ -34,11 +41,11 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = nil
+          body = nil
 
           method = Elasticsearch::API::HTTP_GET
           path   = '_security/user/_privileges'
-          params = {}
+          params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(
             perform_request(method, path, params, body, headers, request_opts)

data/lib/elasticsearch/api/actions/security/get_user_profile.rb

@@ -15,20 +15,27 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Retrieves user profiles for the given unique ID(s).
+        # Get a user profile.
+        # Get a user's profile using the unique profile ID.
+        # NOTE: The user profile feature is designed only for use by Kibana and Elastic's Observability, Enterprise Search, and Elastic Security solutions.
+        # Individual users and external applications should not call this API directly.
+        # Elastic reserves the right to change or remove this feature in future releases without prior notice.
         #
-        # @option arguments [List] :uid A comma-separated list of unique identifier for user profiles
-        # @option arguments [List] :data A comma-separated list of keys for which the corresponding application data are retrieved.
+        # @option arguments [Userprofileid] :uid A unique identifier for the user profile. (*Required*)
+        # @option arguments [String] :data A comma-separated list of filters for the +data+ field of the profile document.
+        #  To return all content use +data=*+.
+        #  To return a subset of content use +data=<key>+ to retrieve content nested under the specified +<key>+.
+        #  By default returns no +data+ content.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-get-user-profile.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-get-user-profile
         #
         def get_user_profile(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.get_user_profile' }
@@ -43,12 +50,12 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = nil
+          body = nil
 
           _uid = arguments.delete(:uid)
 
           method = Elasticsearch::API::HTTP_GET
-          path   = "_security/profile/#{Utils.__listify(_uid)}"
+          path   = "_security/profile/#{Utils.listify(_uid)}"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/security/grant_api_key.rb

@@ -15,20 +15,34 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Creates an API key on behalf of another user.
+        # Grant an API key.
+        # Create an API key on behalf of another user.
+        # This API is similar to the create API keys API, however it creates the API key for a user that is different than the user that runs the API.
+        # The caller must have authentication credentials for the user on whose behalf the API key will be created.
+        # It is not possible to use this API to create an API key without that user's credentials.
+        # The supported user authentication credential types are:
+        # * username and password
+        # * Elasticsearch access tokens
+        # * JWTs
+        # The user, for whom the authentication credentials is provided, can optionally "run as" (impersonate) another user.
+        # In this case, the API key will be created on behalf of the impersonated user.
+        # This API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.
+        # The API keys are created by the Elasticsearch API key service, which is automatically enabled.
+        # A successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.
+        # If applicable, it also returns expiration information for the API key in milliseconds.
+        # By default, API keys never expire. You can specify expiration information when you create the API keys.
         #
-        # @option arguments [String] :refresh If `true` (the default) then refresh the affected shards to make this operation visible to search, if `wait_for` then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. (options: true, false, wait_for)
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The api key request to create an API key (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-grant-api-key.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-grant-api-key
         #
         def grant_api_key(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.grant_api_key' }
@@ -38,11 +52,11 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_POST
           path   = '_security/api_key/grant'
-          params = Utils.process_params(arguments)
+          params = {}
 
           Elasticsearch::API::Response.new(
             perform_request(method, path, params, body, headers, request_opts)

data/lib/elasticsearch/api/actions/security/has_privileges.rb

@@ -15,20 +15,23 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Determines whether the specified user has a specified list of privileges.
+        # Check user privileges.
+        # Determine whether the specified user has a specified list of privileges.
+        # All users can use this API, but only to determine their own privileges.
+        # To check the privileges of other users, you must use the run as feature.
         #
         # @option arguments [String] :user Username
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The privileges to test (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-has-privileges.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-has-privileges
         #
         def has_privileges(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.has_privileges' }
@@ -49,7 +52,7 @@ module Elasticsearch
 
           method = Elasticsearch::API::HTTP_POST
           path   = if _user
-                     "_security/user/#{Utils.__listify(_user)}/_has_privileges"
+                     "_security/user/#{Utils.listify(_user)}/_has_privileges"
                    else
                      '_security/user/_has_privileges'
                    end

data/lib/elasticsearch/api/actions/security/has_privileges_user_profile.rb

@@ -15,19 +15,22 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Determines whether the users associated with the specified profile IDs have all the requested privileges.
+        # Check user profile privileges.
+        # Determine whether the users associated with the specified user profile IDs have all the requested privileges.
+        # NOTE: The user profile feature is designed only for use by Kibana and Elastic's Observability, Enterprise Search, and Elastic Security solutions. Individual users and external applications should not call this API directly.
+        # Elastic reserves the right to change or remove this feature in future releases without prior notice.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The privileges to check and the list of profile IDs (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-has-privileges-user-profile.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-has-privileges-user-profile
         #
         def has_privileges_user_profile(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.has_privileges_user_profile' }
@@ -37,7 +40,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_POST
           path   = '_security/profile/_has_privileges'

data/lib/elasticsearch/api/actions/security/invalidate_api_key.rb

@@ -15,19 +15,29 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Invalidates one or more API keys.
+        # Invalidate API keys.
+        # This API invalidates API keys created by the create API key or grant API key APIs.
+        # Invalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted.
+        # To use this API, you must have at least the +manage_security+, +manage_api_key+, or +manage_own_api_key+ cluster privileges.
+        # The +manage_security+ privilege allows deleting any API key, including both REST and cross cluster API keys.
+        # The +manage_api_key+ privilege allows deleting any REST API key, but not cross cluster API keys.
+        # The +manage_own_api_key+ only allows deleting REST API keys that are owned by the user.
+        # In addition, with the +manage_own_api_key+ privilege, an invalidation request must be issued in one of the three formats:
+        # - Set the parameter +owner=true+.
+        # - Or, set both +username+ and +realm_name+ to match the user's identity.
+        # - Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the +ids+ field.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The api key request to invalidate API key(s) (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-invalidate-api-key.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-invalidate-api-key
         #
         def invalidate_api_key(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.invalidate_api_key' }
@@ -37,7 +47,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_DELETE
           path   = '_security/api_key'

data/lib/elasticsearch/api/actions/security/invalidate_token.rb

@@ -15,19 +15,28 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Invalidates one or more access tokens or refresh tokens.
+        # Invalidate a token.
+        # The access tokens returned by the get token API have a finite period of time for which they are valid.
+        # After that time period, they can no longer be used.
+        # The time period is defined by the +xpack.security.authc.token.timeout+ setting.
+        # The refresh tokens returned by the get token API are only valid for 24 hours.
+        # They can also be used exactly once.
+        # If you want to invalidate one or more access or refresh tokens immediately, use this invalidate token API.
+        # NOTE: While all parameters are optional, at least one of them is required.
+        # More specifically, either one of +token+ or +refresh_token+ parameters is required.
+        # If none of these two are specified, then +realm_name+ and/or +username+ need to be specified.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The token to invalidate (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-invalidate-token.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-invalidate-token
         #
         def invalidate_token(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.invalidate_token' }
@@ -37,7 +46,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_DELETE
           path   = '_security/oauth2/token'

data/lib/elasticsearch/api/actions/security/oidc_authenticate.rb

@@ -15,19 +15,22 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Exchanges an OpenID Connection authentication response message for an Elasticsearch access token and refresh token pair
+        # Authenticate OpenID Connect.
+        # Exchange an OpenID Connect authentication response message for an Elasticsearch internal access token and refresh token that can be subsequently used for authentication.
+        # Elasticsearch exposes all the necessary OpenID Connect related functionality with the OpenID Connect APIs.
+        # These APIs are used internally by Kibana in order to provide OpenID Connect based authentication, but can also be used by other, custom web applications or other clients.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The OpenID Connect response to authenticate (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-oidc-authenticate.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-oidc-authenticate
         #
         def oidc_authenticate(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.oidc_authenticate' }
@@ -37,7 +40,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_POST
           path   = '_security/oidc/authenticate'

data/lib/elasticsearch/api/actions/security/oidc_logout.rb

@@ -15,19 +15,23 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Invalidates a refresh token and access token that was generated from the OpenID Connect Authenticate API
+        # Logout of OpenID Connect.
+        # Invalidate an access token and a refresh token that were generated as a response to the +/_security/oidc/authenticate+ API.
+        # If the OpenID Connect authentication realm in Elasticsearch is accordingly configured, the response to this call will contain a URI pointing to the end session endpoint of the OpenID Connect Provider in order to perform single logout.
+        # Elasticsearch exposes all the necessary OpenID Connect related functionality with the OpenID Connect APIs.
+        # These APIs are used internally by Kibana in order to provide OpenID Connect based authentication, but can also be used by other, custom web applications or other clients.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body Access token and refresh token to invalidate (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-oidc-logout.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-oidc-logout
         #
         def oidc_logout(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.oidc_logout' }
@@ -37,7 +41,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_POST
           path   = '_security/oidc/logout'

data/lib/elasticsearch/api/actions/security/oidc_prepare_authentication.rb

@@ -15,19 +15,23 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Creates an OAuth 2.0 authentication request as a URL string
+        # Prepare OpenID connect authentication.
+        # Create an oAuth 2.0 authentication request as a URL string based on the configuration of the OpenID Connect authentication realm in Elasticsearch.
+        # The response of this API is a URL pointing to the Authorization Endpoint of the configured OpenID Connect Provider, which can be used to redirect the browser of the user in order to continue the authentication process.
+        # Elasticsearch exposes all the necessary OpenID Connect related functionality with the OpenID Connect APIs.
+        # These APIs are used internally by Kibana in order to provide OpenID Connect based authentication, but can also be used by other, custom web applications or other clients.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The OpenID Connect authentication realm configuration (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-oidc-prepare-authentication.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-oidc-prepare-authentication
         #
         def oidc_prepare_authentication(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.oidc_prepare_authentication' }
@@ -37,7 +41,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_POST
           path   = '_security/oidc/prepare'

data/lib/elasticsearch/api/actions/security/put_privileges.rb

@@ -15,20 +15,32 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Adds or updates application privileges.
+        # Create or update application privileges.
+        # To use this API, you must have one of the following privileges:
+        # * The +manage_security+ cluster privilege (or a greater privilege such as +all+).
+        # * The "Manage Application Privileges" global privilege for the application being referenced in the request.
+        # Application names are formed from a prefix, with an optional suffix that conform to the following rules:
+        # * The prefix must begin with a lowercase ASCII letter.
+        # * The prefix must contain only ASCII letters or digits.
+        # * The prefix must be at least 3 characters long.
+        # * If the suffix exists, it must begin with either a dash +-+ or +_+.
+        # * The suffix cannot contain any of the following characters: +\+, +/+, +*+, +?+, +"+, +<+, +>+, +|+, +,+, +*+.
+        # * No part of the name can contain whitespace.
+        # Privilege names must begin with a lowercase ASCII letter and must contain only ASCII letters and digits along with the characters +_+, +-+, and +.+.
+        # Action names can contain any number of printable ASCII characters and must contain at least one of the following characters: +/+, +*+, +:+.
         #
-        # @option arguments [String] :refresh If `true` (the default) then refresh the affected shards to make this operation visible to search, if `wait_for` then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. (options: true, false, wait_for)
+        # @option arguments [String] :refresh If +true+ (the default) then refresh the affected shards to make this operation visible to search, if +wait_for+ then wait for a refresh to make this operation visible to search, if +false+ then do nothing with refreshes.
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The privilege(s) to add (*Required*)
+        # @option arguments [Hash] :body privileges
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-put-privileges.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-put-privileges
         #
         def put_privileges(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.put_privileges' }
@@ -38,7 +50,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           method = Elasticsearch::API::HTTP_PUT
           path   = '_security/privilege'

data/lib/elasticsearch/api/actions/security/put_role.rb

@@ -15,21 +15,24 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Adds and updates roles in the native realm.
+        # Create or update roles.
+        # The role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management.
+        # The create or update roles API cannot update roles that are defined in roles files.
+        # File-based role management is not available in Elastic Serverless.
         #
-        # @option arguments [String] :name Role name
-        # @option arguments [String] :refresh If `true` (the default) then refresh the affected shards to make this operation visible to search, if `wait_for` then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. (options: true, false, wait_for)
+        # @option arguments [String] :name The name of the role that is being created or updated. On Elasticsearch Serverless, the role name must begin with a letter or digit and can only contain letters, digits and the characters '_', '-', and '.'. Each role must have a unique name, as this will serve as the identifier for that role. (*Required*)
+        # @option arguments [String] :refresh If +true+ (the default) then refresh the affected shards to make this operation visible to search, if +wait_for+ then wait for a refresh to make this operation visible to search, if +false+ then do nothing with refreshes.
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The role to add (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-put-role.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-put-role
         #
         def put_role(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.put_role' }
@@ -50,7 +53,7 @@ module Elasticsearch
           _name = arguments.delete(:name)
 
           method = Elasticsearch::API::HTTP_PUT
-          path   = "_security/role/#{Utils.__listify(_name)}"
+          path   = "_security/role/#{Utils.listify(_name)}"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/security/put_role_mapping.rb

@@ -15,21 +15,39 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Security
       module Actions
-        # Creates and updates role mappings.
+        # Create or update role mappings.
+        # Role mappings define which roles are assigned to each user.
+        # Each mapping has rules that identify users and a list of roles that are granted to those users.
+        # The role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files.
+        # NOTE: This API does not create roles. Rather, it maps users to existing roles.
+        # Roles can be created by using the create or update roles API or roles files.
+        # **Role templates**
+        # The most common use for role mappings is to create a mapping from a known value on the user to a fixed role name.
+        # For example, all users in the +cn=admin,dc=example,dc=com+ LDAP group should be given the superuser role in Elasticsearch.
+        # The +roles+ field is used for this purpose.
+        # For more complex needs, it is possible to use Mustache templates to dynamically determine the names of the roles that should be granted to the user.
+        # The +role_templates+ field is used for this purpose.
+        # NOTE: To use role templates successfully, the relevant scripting feature must be enabled.
+        # Otherwise, all attempts to create a role mapping with role templates fail.
+        # All of the user fields that are available in the role mapping rules are also available in the role templates.
+        # Thus it is possible to assign a user to a role that reflects their username, their groups, or the name of the realm to which they authenticated.
+        # By default a template is evaluated to produce a single string that is the name of the role which should be assigned to the user.
+        # If the format of the template is set to "json" then the template is expected to produce a JSON string or an array of JSON strings for the role names.
         #
-        # @option arguments [String] :name Role-mapping name
-        # @option arguments [String] :refresh If `true` (the default) then refresh the affected shards to make this operation visible to search, if `wait_for` then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. (options: true, false, wait_for)
+        # @option arguments [String] :name The distinct name that identifies the role mapping.
+        #  The name is used solely as an identifier to facilitate interaction via the API; it does not affect the behavior of the mapping in any way. (*Required*)
+        # @option arguments [String] :refresh If +true+ (the default) then refresh the affected shards to make this operation visible to search, if +wait_for+ then wait for a refresh to make this operation visible to search, if +false+ then do nothing with refreshes.
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The role mapping to add (*Required*)
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/security-api-put-role-mapping.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-security-put-role-mapping
         #
         def put_role_mapping(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'security.put_role_mapping' }
@@ -50,7 +68,7 @@ module Elasticsearch
           _name = arguments.delete(:name)
 
           method = Elasticsearch::API::HTTP_PUT
-          path   = "_security/role_mapping/#{Utils.__listify(_name)}"
+          path   = "_security/role_mapping/#{Utils.listify(_name)}"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(