Class ListEndpointsRequest (0.2.0)

Stay organized with collections Save and categorize content based on your preferences.
ListEndpointsRequest(mapping=None, *, ignore_unknown_fields=False, **kwargs)

The request message for RegistrationService.ListEndpoints.


parent str
Required. The resource name of the service whose endpoints we'd like to list.
page_size int
Optional. The maximum number of items to return.
page_token str
Optional. The next_page_token value returned from a previous List request, if any.
filter str
Optional. The filter to list result by. General filter string syntax: () can be "name", "address", "port" or "metadata." for map field. can be "<,>, <=,>=, !=, =, :". Of which ":" means HAS, and is roughly the same as "=". must be the same data type as field. can be "AND, OR, NOT". Examples of valid filters: - "metadata.owner" returns Endpoints that have a label with the key "owner" this is the same as "metadata:owner". - "metadata.protocol=gRPC" returns Endpoints that have key/value "protocol=gRPC". - "address=" returns Endpoints that have this address. - "port>8080" returns Endpoints that have port number larger than 8080. - "name>projects/my-project/locations/us-east/namespaces/my-namespace/services/my-service/endpoints/endpoint-c" returns Endpoints that have name that is alphabetically later than the string, so "endpoint-e" will be returned but "endpoint-a" will not be. - "metadata.owner!=sd AND" returns Endpoints that have "owner" in label key but value is not "sd" AND have key/value 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.
order_by str
Optional. The order to list result by.


builtins.object > proto.message.Message > ListEndpointsRequest




Delete the value on the given field.

This is generally equivalent to setting a falsy value.



Return True if the messages are equal, False otherwise.



Return True if the messages are unequal, False otherwise.


__setattr__(key, value)

Set the value on the given field.

For well-known protocol buffer types which are marshalled, either the protocol buffer object or the Python equivalent is accepted.