Skip to main content

database_roles_iam_policies

Creates, updates, deletes, gets or lists a database_roles_iam_policies resource.

Overview

Namedatabase_roles_iam_policies
TypeResource
Idgoogle.spanner.database_roles_iam_policies

Fields

The following fields are returned by SELECT queries:

SELECT not supported for this resource, use SHOW METHODS to view available operations for the resource.

Methods

The following methods are available for this resource:

NameAccessible byRequired ParamsOptional ParamsDescription
projects_instances_databases_database_roles_test_iam_permissionsexecprojectsId, instancesId, databasesId, databaseRolesIdReturns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has spanner.databases.list permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has spanner.backups.list permission on the containing instance. Calling this method on a backup schedule that does not exist will result in a NOT_FOUND error if the user has spanner.backupSchedules.list permission on the containing database.

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

NameDatatypeDescription
databaseRolesIdstring
databasesIdstring
instancesIdstring
projectsIdstring

Lifecycle Methods

Returns permissions that the caller has on the specified database or backup resource. Attempting this RPC on a non-existent Cloud Spanner database will result in a NOT_FOUND error if the user has spanner.databases.list permission on the containing Cloud Spanner instance. Otherwise returns an empty set of permissions. Calling this method on a backup that does not exist will result in a NOT_FOUND error if the user has spanner.backups.list permission on the containing instance. Calling this method on a backup schedule that does not exist will result in a NOT_FOUND error if the user has spanner.backupSchedules.list permission on the containing database.

EXEC google.spanner.database_roles_iam_policies.projects_instances_databases_database_roles_test_iam_permissions 
@projectsId='{{ projectsId }}' --required,
@instancesId='{{ instancesId }}' --required,
@databasesId='{{ databasesId }}' --required,
@databaseRolesId='{{ databaseRolesId }}' --required
@@json=
'{
"permissions": "{{ permissions }}"
}';