List
Retrieves a list of SQL Server users in the specified cluster.
- TypeScript
- Python
import { cloudApi, serviceClients, Session } from "@yandex-cloud/nodejs-sdk";
const ListUsersRequest = cloudApi.mdb.clickhouse_user_service.ListUsersRequest;
(async () => {
const authToken = process.env["YC_OAUTH_TOKEN"];
const session = new Session({ oauthToken: authToken });
const client = session.client(serviceClients.UserServiceClient);
const result = await client.list(
ListUsersRequest.fromPartial({
clusterId: "clusterId",
// pageSize: 0,
// pageToken: "pageToken"
})
);
console.log(result);
})();
import os
import grpc
import yandexcloud
from yandex.cloud.mdb.clickhouse.v1.user_service_pb2 import ListUsersRequest
from yandex.cloud.mdb.clickhouse.v1.user_service_pb2_grpc import UserServiceStub
token = os.getenv("YC_OAUTH_TOKEN")
sdk = yandexcloud.SDK(token=token)
service = sdk.client(UserServiceStub)
response = service.List(
ListUsersRequest(
cluster_id="clusterId",
# page_size = 0,
# page_token = "pageToken"
)
)
print(response)
ListUsersRequest
clusterId : string
ID of the cluster to list SQL Server users in.
To get the cluster ID, use a ClusterService.List request.
pageSize : int64
The maximum number of results per page to return.
If the number of available results is larger than page_size, the service returns a ListUsersResponse.next_page_token that can be used to get the next page of results in subsequent list requests.
pageToken : string
Page token. To get the next page of results, set page_token to the ListUsersResponse.next_page_token returned by the previous list request.
ListUsersResponse
users : User
Requested list of SQL Server users.
nextPageToken : string
Token that allows you to get the next page of results for list requests.
If the number of results is larger than ListUsersRequest.page_size, use the next_page_token as the value for the ListUsersRequest.page_token parameter in the next list request.
Each subsequent list request has its own next_page_token to continue paging through the results.
User
An SQL Server user.
name : string
Name of the SQL Server user.
clusterId : string
ID of the SQL Server cluster the user belongs to.
permissions : Permission
Set of permissions granted to the user.
serverRoles : ServerRole
Set of server roles granted to the login.
Permission
Role
Role granted to the user within the database.
ROLE_UNSPECIFIEDRole granted to the user within the database.
DB_OWNERMembers of this fixed database role can perform all configuration and maintenance activities on a database and can also drop a database in SQL Server.
DB_SECURITYADMINMembers of this fixed database role can modify role membership for custom roles only and manage permissions. They can potentially elevate their privileges and their actions should be monitored.
DB_ACCESSADMINMembers of this fixed database role can add or remove access to a database for Windows logins, Windows groups, and SQL Server logins.
DB_BACKUPOPERATORMembers of this fixed database role can back up the database.
DB_DDLADMINMembers of this fixed database role can run any Data Definition Language (DDL) command in a database.
DB_DATAWRITERMembers of this fixed database role can add, delete, or change data in all user tables.
DB_DATAREADERMembers of this fixed database role can read all data from all user tables.
DB_DENYDATAWRITERMembers of this fixed database role cannot add, modify, or delete any data in the user tables within a database. A denial has a higher priority than a grant, so you can use this role to quickly restrict one's privileges without explicitly revoking permissions or roles.
DB_DENYDATAREADERMembers of this fixed database role cannot read any data in the user tables within a database. A denial has a higher priority than a grant, so you can use this role to quickly restrict one's privileges without explicitly revoking permissions or roles.
databaseName : string
Name of the database the permission grants access to.
roles : Role
Roles granted to the user within the database.