Use ModifyUserGroups to change user groups - Elastic High Performance Computing - Alibaba Cloud - Elastic High Performance Computing

Changes the user group to which users belong.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

ehpc:ModifyUserGroups

update

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
ClusterId	string	Yes	The cluster ID. You can call the ListClusters operation to obtain the cluster ID.	ehpc-hz-FYUr32****
User	array<object>	Yes	The users. You can specify 1 to 100 users.
	object	No	The array of user information.
Name	string	No	The username. You can call the ListUsers operation to query the usernames in the cluster.	user11
Group	string	No	The user group to be changed. Valid values: users: ordinary permissions, which are suitable for ordinary users that need only to submit and debug jobs. wheel: sudo permissions, which are suitable for administrators who need to manage clusters. In addition to submitting and debugging jobs, you can also run sudo commands to install software and restart nodes.	users
Async	boolean	No	Specifies whether to use asynchronous message links to change the user group. Default value: false.	false

Response elements

Element	Type	Description	Example
	object
RequestId	string	The ID of the request.	04F0F334-1335-436C-A1D7-6C044FE7****

Examples

Success response

JSON format

{
  "RequestId": "04F0F334-1335-436C-A1D7-6C044FE7****"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParams	The specified parameter %s is invalid.	The specified parameter %s is invalid.
400	NotEnabled	You have not enabled this service	You have not enabled this service
400	InDebt	Your account has overdue payments.	Your account has overdue payments.
400	InvalidOpt	The specified operation is invalid. Please try again later. If the problem still exists, submit a ticket.
500	UnknownError	An unknown error occurred.	An unknown error occurred.
403	InvalidClusterStatus	The operation failed due to invalid cluster status.	The cluster status does not support the operation.
404	ClusterNotFound	The specified cluster does not exist.	The specified instance does not exist.
404	ManagerNotFound	The manager nodes do not exist or their status is abnormal.	The manager nodes do not exist or their status is abnormal.
503	ServiceUnavailable	The request has failed due to a temporary failure of the server	The request has failed due to a temporary failure of the server.
406	AgentError	The agent service request failed.	The cluster-side command failed to run. %s
406	AgentError.Account.DomainNotExist	The specified domain does not exist: %s.	The domain service does not exist: %s
406	AgentError.Account.GetentPasswdFailure	Failed to get the user list: %s.	Failed to obtain the domain user list: %s
406	AgentError.Account.UserAlreadyExist	The specified user already exists in domain: %s.	The user already exists in domain: %s
406	AgentError.Account.UserAddFailure	Failed to add user to domain: %s.	Failed to add the user to domain: %s
406	AgentError.Account.UserNotExist	The specified user is not found in the domain: %s.	The user does not exist in the domain: %s.
406	AgentError.Account.UserModifyGroupFailure	Failed to modify user groups in domain: %s.	Failed to modify the user permission group: %s
407	NotAuthorized	You are not authorized by RAM for this request.	The request is not authorized by RAM.
409	PartFailure	Part of the batch operation failed.	Part of the batch operation failed.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.