API documentation for compute_v1.services.region_commitments.pagers
module.
Classes
AggregatedListPager
AggregatedListPager(
method: typing.Callable[
[...], google.cloud.compute_v1.types.compute.CommitmentAggregatedList
],
request: google.cloud.compute_v1.types.compute.AggregatedListRegionCommitmentsRequest,
response: google.cloud.compute_v1.types.compute.CommitmentAggregatedList,
*,
retry: typing.Optional[
typing.Union[
google.api_core.retry.retry_unary.Retry,
google.api_core.gapic_v1.method._MethodDefault,
]
] = _MethodDefault._DEFAULT_VALUE,
timeout: typing.Union[float, object] = _MethodDefault._DEFAULT_VALUE,
metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)
A pager for iterating through aggregated_list
requests.
This class thinly wraps an initial
CommitmentAggregatedList object, and
provides an __iter__
method to iterate through its
items
field.
If there are more pages, the __iter__
method will make additional
AggregatedList
requests and continue to iterate
through the items
field on the
corresponding responses.
All the usual CommitmentAggregatedList attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.
ListPager
ListPager(
method: typing.Callable[
[...], google.cloud.compute_v1.types.compute.CommitmentList
],
request: google.cloud.compute_v1.types.compute.ListRegionCommitmentsRequest,
response: google.cloud.compute_v1.types.compute.CommitmentList,
*,
retry: typing.Optional[
typing.Union[
google.api_core.retry.retry_unary.Retry,
google.api_core.gapic_v1.method._MethodDefault,
]
] = _MethodDefault._DEFAULT_VALUE,
timeout: typing.Union[float, object] = _MethodDefault._DEFAULT_VALUE,
metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)
A pager for iterating through list
requests.
This class thinly wraps an initial
CommitmentList object, and
provides an __iter__
method to iterate through its
items
field.
If there are more pages, the __iter__
method will make additional
List
requests and continue to iterate
through the items
field on the
corresponding responses.
All the usual CommitmentList attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.