Module pagers (1.8.3)

Version 1.8.3

• 1.18.1 (latest)
• 1.18.0
• 1.16.5
• 1.15.0
• 1.14.0
• 1.13.2
• 1.12.0
• 1.11.0
• 1.10.1
• 1.9.0
• 1.8.3
• 1.7.0
• 1.6.0
• 1.5.2
• 1.4.0
• 1.3.1
• 1.2.0
• 1.1.1
• 1.0.4
• 0.7.2
• 0.6.1
• 0.5.1
• 0.4.0
• 0.1.0

API documentation for functions_v1.services.cloud_functions_service.pagers module.

Classes

ListFunctionsAsyncPager

ListFunctionsAsyncPager(
    method: Callable[
        [...],
        Awaitable[google.cloud.functions_v1.types.functions.ListFunctionsResponse],
    ],
    request: google.cloud.functions_v1.types.functions.ListFunctionsRequest,
    response: google.cloud.functions_v1.types.functions.ListFunctionsResponse,
    *,
    metadata: Sequence[Tuple[str, str]] = ()
)

A pager for iterating through list_functions requests.

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

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

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

ListFunctionsPager

ListFunctionsPager(
    method: Callable[
        [...], google.cloud.functions_v1.types.functions.ListFunctionsResponse
    ],
    request: google.cloud.functions_v1.types.functions.ListFunctionsRequest,
    response: google.cloud.functions_v1.types.functions.ListFunctionsResponse,
    *,
    metadata: Sequence[Tuple[str, str]] = ()
)

A pager for iterating through list_functions requests.

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

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

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