Module pagers (2.15.2)

Version 2.15.2

• 2.16.1 (latest)
• 2.16.0
• 2.15.5
• 2.14.0
• 2.13.1
• 2.12.1
• 2.11.1
• 2.10.0
• 2.9.3
• 2.8.1
• 2.7.1
• 2.6.0
• 2.5.1
• 2.4.1
• 2.3.0
• 2.2.4
• 2.1.1
• 2.0.0
• 1.0.2
• 0.4.0
• 0.3.0

API documentation for redis_v1.services.cloud_redis.pagers module.

Classes

ListInstancesAsyncPager

ListInstancesAsyncPager(
    method: typing.Callable[
        [...],
        typing.Awaitable[google.cloud.redis_v1.types.cloud_redis.ListInstancesResponse],
    ],
    request: google.cloud.redis_v1.types.cloud_redis.ListInstancesRequest,
    response: google.cloud.redis_v1.types.cloud_redis.ListInstancesResponse,
    *,
    metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)

A pager for iterating through list_instances requests.

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

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

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

ListInstancesPager

ListInstancesPager(
    method: typing.Callable[
        [...], google.cloud.redis_v1.types.cloud_redis.ListInstancesResponse
    ],
    request: google.cloud.redis_v1.types.cloud_redis.ListInstancesRequest,
    response: google.cloud.redis_v1.types.cloud_redis.ListInstancesResponse,
    *,
    metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)

A pager for iterating through list_instances requests.

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

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

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