CloudWatchLogs get_log_events should have paginator

[thehesiod]

given it returns pages of results and has a nextToken

[kyleknap]

I think it makes sense to have a paginator for this one. The only reason we do not is that it cannot be supported in our current pagination model schema. There is more context here: #613, but essentially we need context in which way we want to consume pagination tokens base on the startFromHead parameter and our pagination models do not support that. This may require either an update to our pagination model schema or a one off customization. Marking as enhancement.

[thehesiod]

would a v2 of the API help?

[kyleknap]

That could help, but would have to be driven from the service team. I think the best/most immediate option would be to update our pagination specification to support this use case or do the one-off customization as that is more in the library's control.

[copumpkin]

IMO it would be great to have two paginators for this API, one going forwards and the other backwards. If the model gets adapted to support the unusual API, it would be nice if it could support backwards pagination too.

I also think it's unusual enough to be worth just allowing individual service-specific custom paginators, and not revamping the broader model.

[PatMyron]

related: #1462

[tim-finnigan]

These are the current paginators available for CloudWatchLogs: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/logs.html#paginators.

As mentioned in #1462 (comment), service teams now own their respective paginator model definitions since they are shared across SDKs. I created a new issue for tracking this specific feature request here in our cross-SDK repository: aws/aws-sdk#422. I also reached out to the CloudWatch Logs team to see if this is something that they can implement. Please refer to that new issue for updates going forward.