Module pagers (1.7.2)

Version 1.7.2

• 1.11.1 (latest)
• 1.11.0
• 1.10.5
• 1.9.0
• 1.7.2
• 1.6.1
• 1.5.0
• 1.4.3
• 1.3.2
• 1.2.1
• 1.1.0
• 1.0.1
• 0.2.2
• 0.1.0

API documentation for service_usage_v1.services.service_usage.pagers module.

Classes

ListServicesAsyncPager

ListServicesAsyncPager(
    method: typing.Callable[
        [...],
        typing.Awaitable[
            google.cloud.service_usage_v1.types.serviceusage.ListServicesResponse
        ],
    ],
    request: google.cloud.service_usage_v1.types.serviceusage.ListServicesRequest,
    response: google.cloud.service_usage_v1.types.serviceusage.ListServicesResponse,
    *,
    metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)

A pager for iterating through list_services requests.

This class thinly wraps an initial ListServicesResponse object, and provides an __aiter__ method to iterate through its services field.

If there are more pages, the __aiter__ method will make additional ListServices requests and continue to iterate through the services field on the corresponding responses.

All the usual ListServicesResponse attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.

ListServicesPager

ListServicesPager(
    method: typing.Callable[
        [...], google.cloud.service_usage_v1.types.serviceusage.ListServicesResponse
    ],
    request: google.cloud.service_usage_v1.types.serviceusage.ListServicesRequest,
    response: google.cloud.service_usage_v1.types.serviceusage.ListServicesResponse,
    *,
    metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)

A pager for iterating through list_services requests.

This class thinly wraps an initial ListServicesResponse object, and provides an __iter__ method to iterate through its services field.

If there are more pages, the __iter__ method will make additional ListServices requests and continue to iterate through the services field on the corresponding responses.

All the usual ListServicesResponse attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.