Service Directory API for registering services. It defines the following
resource model:
The API has a collection of
Namespace
resources, named projects/* /locations/* /namespaces/*.
Each Namespace has a collection of
Service resources, named
projects/* /locations/* /namespaces/* /services/*.
Each Service has a collection of
Endpoint
resources, named
projects/* /locations/* /namespaces/* /services/* /endpoints/*.
Constructor
new RegistrationServiceClient(optionsopt)
Construct an instance of RegistrationServiceClient.
Parameters:
Name
Type
Attributes
Description
options
object
<optional>
The configuration object.
The options accepted by the constructor are described in detail
in this document.
The common options are:
Properties
Name
Type
Attributes
Description
credentials
object
<optional>
Credentials object.
Properties
Name
Type
Attributes
Description
client_email
string
<optional>
private_key
string
<optional>
email
string
<optional>
Account email address. Required when
using a .pem or .p12 keyFilename.
keyFilename
string
<optional>
Full path to the a .json, .pem, or
.p12 key downloaded from the Google Developers Console. If you provide
a path to a JSON file, the projectId option below is not necessary.
NOTE: .pem and .p12 require you to specify options.email as well.
port
number
<optional>
The port on which to connect to
the remote host.
projectId
string
<optional>
The project ID from the Google
Developer's Console, e.g. 'grape-spaceship-123'. We will also check
the environment variable GCLOUD_PROJECT for your project ID. If your
app is running in an environment which supports
Application Default Credentials,
your project ID will be detected automatically.
apiEndpoint
string
<optional>
The domain name of the
API remote host.
clientConfig
gax.ClientConfig
<optional>
Client configuration override.
Follows the structure of gapicConfig.
fallback
boolean
<optional>
Use HTTP fallback mode.
In fallback mode, a special browser-compatible transport implementation is used
instead of gRPC transport. In browser context (if the window object is defined)
the fallback mode is enabled automatically; set options.fallback to false
if you need to override this behavior.
Members
apiEndpoint
The DNS address for this API service - same as servicePath(),
exists for compatibility reasons.
port
The port for this API service.
scopes
The scopes needed to make gRPC calls for every method defined
in this service.
servicePath
The DNS address for this API service.
Methods
close() → {Promise}
Terminate the gRPC channel and close the client.
The client will no longer be usable and all future behavior is undefined.
Returns:
Type
Description
Promise
A promise that resolves when the client is closed.
createEndpoint(request, optionsopt) → {Promise}
Creates an endpoint, and returns the new endpoint.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Description
parent
string
Required. The resource name of the service that this endpoint provides.
endpointId
string
Required. The Resource ID must be 1-63 characters long, and comply with
RFC1035.
Specifically, the name must be 1-63 characters long and match the regular
expression [a-z](?:[-a-z0-9]{0,61}[a-z0-9])? which means the first
character must be a lowercase letter, and all following characters must
be a dash, lowercase letter, or digit, except the last character, which
cannot be a dash.
The promise which resolves to an array.
The first element of the array is an object representing Endpoint.
Please see the
documentation
for more details and examples.
Creates a namespace, and returns the new namespace.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Description
parent
string
Required. The resource name of the project and location the namespace
will be created in.
namespaceId
string
Required. The Resource ID must be 1-63 characters long, and comply with
RFC1035.
Specifically, the name must be 1-63 characters long and match the regular
expression [a-z](?:[-a-z0-9]{0,61}[a-z0-9])? which means the first
character must be a lowercase letter, and all following characters must
be a dash, lowercase letter, or digit, except the last character, which
cannot be a dash.
The promise which resolves to an array.
The first element of the array is an object representing Namespace.
Please see the
documentation
for more details and examples.
Required. The resource name of the namespace this service will belong to.
serviceId
string
Required. The Resource ID must be 1-63 characters long, and comply with
RFC1035.
Specifically, the name must be 1-63 characters long and match the regular
expression [a-z](?:[-a-z0-9]{0,61}[a-z0-9])? which means the first
character must be a lowercase letter, and all following characters must
be a dash, lowercase letter, or digit, except the last character, which
cannot be a dash.
The promise which resolves to an array.
The first element of the array is an object representing Service.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Empty.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Empty.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Empty.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Endpoint.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Policy.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Namespace.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Service.
Please see the
documentation
for more details and examples.
Initialize the client.
Performs asynchronous operations (such as authentication) and prepares the client.
This function will be called automatically when any class method is called for the
first time, but if you need to initialize it before calling an actual method,
feel free to call initialize() directly.
You can await on this method if you want to make sure the client is initialized.
Returns:
Type
Description
Promise
A promise that resolves to an authenticated service stub.
listEndpoints(request, optionsopt) → {Promise}
Lists all endpoints.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the service whose endpoints you'd like to
list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request,
if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name, address, port, or metadata.<key> for map
field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
metadata.owner returns endpoints that have a metadata with the key
owner, this is the same as metadata:owner
metadata.protocol=gRPC returns endpoints that have key/value
protocol=gRPC
address=192.108.1.105 returns endpoints that have this address
port>8080 returns endpoints that have port number larger than 8080
name>projects/my-project/locations/us-east1/namespaces/my-namespace/services/my-service/endpoints/endpoint-c
returns endpoints that have name that is alphabetically later than the
string, so "endpoint-e" is returned but "endpoint-a" is not
metadata.owner!=sd AND metadata.foo=bar returns endpoints that have
owner in metadata key but value is not sd AND have key/value
foo=bar
doesnotexist.foo=bar returns an empty list. Note that endpoint
doesn't have a field called "doesnotexist". Since the filter does not
match any endpoints, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows values: name, address, port
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
The promise which resolves to an array.
The first element of the array is Array of Endpoint.
The client library will perform auto-pagination by default: it will call the API as many
times as needed and will merge results from all the pages into this array.
Note that it can affect your quota.
We recommend using listEndpointsAsync()
method described below for async iteration which you can stop as needed.
Please see the
documentation
for more details and examples.
Equivalent to listEndpoints, but returns an iterable object.
for-await-of syntax is used with the iterable to get response elements on-demand.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the service whose endpoints you'd like to
list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request,
if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name, address, port, or metadata.<key> for map
field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
metadata.owner returns endpoints that have a metadata with the key
owner, this is the same as metadata:owner
metadata.protocol=gRPC returns endpoints that have key/value
protocol=gRPC
address=192.108.1.105 returns endpoints that have this address
port>8080 returns endpoints that have port number larger than 8080
name>projects/my-project/locations/us-east1/namespaces/my-namespace/services/my-service/endpoints/endpoint-c
returns endpoints that have name that is alphabetically later than the
string, so "endpoint-e" is returned but "endpoint-a" is not
metadata.owner!=sd AND metadata.foo=bar returns endpoints that have
owner in metadata key but value is not sd AND have key/value
foo=bar
doesnotexist.foo=bar returns an empty list. Note that endpoint
doesn't have a field called "doesnotexist". Since the filter does not
match any endpoints, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows values: name, address, port
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
An iterable Object that allows async iteration.
When you iterate the returned iterable, each element will be an object representing
Endpoint. The API will be called under the hood as needed, once per the page,
so you can stop the iteration when you don't need more results.
Please see the
documentation
for more details and examples.
Example
const iterable = client.listEndpointsAsync(request);
for await (const response of iterable) {
// process response
}
Equivalent to method.name.toCamelCase(), but returns a NodeJS Stream object.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the service whose endpoints you'd like to
list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request,
if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name, address, port, or metadata.<key> for map
field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
metadata.owner returns endpoints that have a metadata with the key
owner, this is the same as metadata:owner
metadata.protocol=gRPC returns endpoints that have key/value
protocol=gRPC
address=192.108.1.105 returns endpoints that have this address
port>8080 returns endpoints that have port number larger than 8080
name>projects/my-project/locations/us-east1/namespaces/my-namespace/services/my-service/endpoints/endpoint-c
returns endpoints that have name that is alphabetically later than the
string, so "endpoint-e" is returned but "endpoint-a" is not
metadata.owner!=sd AND metadata.foo=bar returns endpoints that have
owner in metadata key but value is not sd AND have key/value
foo=bar
doesnotexist.foo=bar returns an empty list. Note that endpoint
doesn't have a field called "doesnotexist". Since the filter does not
match any endpoints, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows values: name, address, port
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
An object stream which emits an object representing Endpoint on 'data' event.
The client library will perform auto-pagination by default: it will call the API as many
times as needed. Note that it can affect your quota.
We recommend using listEndpointsAsync()
method described below for async iteration which you can stop as needed.
Please see the
documentation
for more details and examples.
listNamespaces(request, optionsopt) → {Promise}
Lists all namespaces.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the project and location whose namespaces you'd like
to list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request, if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name or labels.<key> for map field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
labels.owner returns namespaces that have a label with the key
owner, this is the same as labels:owner
labels.owner=sd returns namespaces that have key/value owner=sd
name>projects/my-project/locations/us-east1/namespaces/namespace-c
returns namespaces that have name that is alphabetically later than the
string, so "namespace-e" is returned but "namespace-a" is not
labels.owner!=sd AND labels.foo=bar returns namespaces that have
owner in label key but value is not sd AND have key/value foo=bar
doesnotexist.foo=bar returns an empty list. Note that namespace
doesn't have a field called "doesnotexist". Since the filter does not
match any namespaces, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows value: name
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
The promise which resolves to an array.
The first element of the array is Array of Namespace.
The client library will perform auto-pagination by default: it will call the API as many
times as needed and will merge results from all the pages into this array.
Note that it can affect your quota.
We recommend using listNamespacesAsync()
method described below for async iteration which you can stop as needed.
Please see the
documentation
for more details and examples.
Equivalent to listNamespaces, but returns an iterable object.
for-await-of syntax is used with the iterable to get response elements on-demand.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the project and location whose namespaces you'd like
to list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request, if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name or labels.<key> for map field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
labels.owner returns namespaces that have a label with the key
owner, this is the same as labels:owner
labels.owner=sd returns namespaces that have key/value owner=sd
name>projects/my-project/locations/us-east1/namespaces/namespace-c
returns namespaces that have name that is alphabetically later than the
string, so "namespace-e" is returned but "namespace-a" is not
labels.owner!=sd AND labels.foo=bar returns namespaces that have
owner in label key but value is not sd AND have key/value foo=bar
doesnotexist.foo=bar returns an empty list. Note that namespace
doesn't have a field called "doesnotexist". Since the filter does not
match any namespaces, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows value: name
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
An iterable Object that allows async iteration.
When you iterate the returned iterable, each element will be an object representing
Namespace. The API will be called under the hood as needed, once per the page,
so you can stop the iteration when you don't need more results.
Please see the
documentation
for more details and examples.
Example
const iterable = client.listNamespacesAsync(request);
for await (const response of iterable) {
// process response
}
Equivalent to method.name.toCamelCase(), but returns a NodeJS Stream object.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the project and location whose namespaces you'd like
to list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request, if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name or labels.<key> for map field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
labels.owner returns namespaces that have a label with the key
owner, this is the same as labels:owner
labels.owner=sd returns namespaces that have key/value owner=sd
name>projects/my-project/locations/us-east1/namespaces/namespace-c
returns namespaces that have name that is alphabetically later than the
string, so "namespace-e" is returned but "namespace-a" is not
labels.owner!=sd AND labels.foo=bar returns namespaces that have
owner in label key but value is not sd AND have key/value foo=bar
doesnotexist.foo=bar returns an empty list. Note that namespace
doesn't have a field called "doesnotexist". Since the filter does not
match any namespaces, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows value: name
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
An object stream which emits an object representing Namespace on 'data' event.
The client library will perform auto-pagination by default: it will call the API as many
times as needed. Note that it can affect your quota.
We recommend using listNamespacesAsync()
method described below for async iteration which you can stop as needed.
Please see the
documentation
for more details and examples.
listServices(request, optionsopt) → {Promise}
Lists all services belonging to a namespace.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the namespace whose services you'd
like to list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request,
if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name or metadata.<key> for map field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
metadata.owner returns services that have a metadata with the key
owner, this is the same as metadata:owner
metadata.protocol=gRPC returns services that have key/value
protocol=gRPC
name>projects/my-project/locations/us-east1/namespaces/my-namespace/services/service-c
returns services that have name that is alphabetically later than the
string, so "service-e" is returned but "service-a" is not
metadata.owner!=sd AND metadata.foo=bar returns services that have
owner in metadata key but value is not sd AND have key/value
foo=bar
doesnotexist.foo=bar returns an empty list. Note that service
doesn't have a field called "doesnotexist". Since the filter does not
match any services, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows value: name
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
The promise which resolves to an array.
The first element of the array is Array of Service.
The client library will perform auto-pagination by default: it will call the API as many
times as needed and will merge results from all the pages into this array.
Note that it can affect your quota.
We recommend using listServicesAsync()
method described below for async iteration which you can stop as needed.
Please see the
documentation
for more details and examples.
listServicesAsync(request, optionsopt) → {Object}
Equivalent to listServices, but returns an iterable object.
for-await-of syntax is used with the iterable to get response elements on-demand.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the namespace whose services you'd
like to list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request,
if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name or metadata.<key> for map field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
metadata.owner returns services that have a metadata with the key
owner, this is the same as metadata:owner
metadata.protocol=gRPC returns services that have key/value
protocol=gRPC
name>projects/my-project/locations/us-east1/namespaces/my-namespace/services/service-c
returns services that have name that is alphabetically later than the
string, so "service-e" is returned but "service-a" is not
metadata.owner!=sd AND metadata.foo=bar returns services that have
owner in metadata key but value is not sd AND have key/value
foo=bar
doesnotexist.foo=bar returns an empty list. Note that service
doesn't have a field called "doesnotexist". Since the filter does not
match any services, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows value: name
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
An iterable Object that allows async iteration.
When you iterate the returned iterable, each element will be an object representing
Service. The API will be called under the hood as needed, once per the page,
so you can stop the iteration when you don't need more results.
Please see the
documentation
for more details and examples.
Example
const iterable = client.listServicesAsync(request);
for await (const response of iterable) {
// process response
}
Equivalent to method.name.toCamelCase(), but returns a NodeJS Stream object.
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Attributes
Description
parent
string
Required. The resource name of the namespace whose services you'd
like to list.
pageSize
number
<optional>
Optional. The maximum number of items to return.
pageToken
string
<optional>
Optional. The next_page_token value returned from a previous List request,
if any.
filter
string
<optional>
Optional. The filter to list results by.
General filter string syntax:
<field> <operator> <value> (<logical connector>)
<field> can be name or metadata.<key> for map field
<operator> can be <, >, <=, >=, !=, =, :. Of which :
means HAS, and is roughly the same as =
<value> must be the same data type as field
<logical connector> can be AND, OR, NOT
Examples of valid filters:
metadata.owner returns services that have a metadata with the key
owner, this is the same as metadata:owner
metadata.protocol=gRPC returns services that have key/value
protocol=gRPC
name>projects/my-project/locations/us-east1/namespaces/my-namespace/services/service-c
returns services that have name that is alphabetically later than the
string, so "service-e" is returned but "service-a" is not
metadata.owner!=sd AND metadata.foo=bar returns services that have
owner in metadata key but value is not sd AND have key/value
foo=bar
doesnotexist.foo=bar returns an empty list. Note that service
doesn't have a field called "doesnotexist". Since the filter does not
match any services, it returns no results
For more information about filtering, see
API Filtering.
orderBy
string
<optional>
Optional. The order to list results by.
General order_by string syntax: <field> (<asc|desc>) (,)
<field> allows value: name
<asc|desc> ascending or descending order by <field>. If this is
left blank, asc is used
Note that an empty order_by string results in default order, which is
order by name in ascending order.
An object stream which emits an object representing Service on 'data' event.
The client library will perform auto-pagination by default: it will call the API as many
times as needed. Note that it can affect your quota.
We recommend using listServicesAsync()
method described below for async iteration which you can stop as needed.
Please see the
documentation
for more details and examples.
locationPath(project, location) → {string}
Return a fully-qualified location resource name string.
REQUIRED: The complete policy to be applied to the resource. The size of
the policy is limited to a few 10s of KB. An empty policy is a
valid policy but certain Cloud Platform services (such as Projects)
might reject them.
The promise which resolves to an array.
The first element of the array is an object representing Policy.
Please see the
documentation
for more details and examples.
Tests IAM permissions for a resource (namespace or service only).
Parameters:
Name
Type
Attributes
Description
request
Object
The request object that will be sent.
Properties
Name
Type
Description
resource
string
REQUIRED: The resource for which the policy detail is being requested.
See the operation documentation for the appropriate value for this field.
permissions
Array.<string>
The set of permissions to check for the resource. Permissions with
wildcards (such as '' or 'storage.') are not allowed. For more
information see
IAM Overview.
The promise which resolves to an array.
The first element of the array is an object representing TestIamPermissionsResponse.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Endpoint.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Namespace.
Please see the
documentation
for more details and examples.
The promise which resolves to an array.
The first element of the array is an object representing Service.
Please see the
documentation
for more details and examples.