CloudWatch Logs's GetLogEvents paginator never terminates

[ianbotsf]

Describe the bug

The CloudWatch Logs client supports a paginator over GetLogEvents but using this paginator yields a never-ending Flow. The service API documentation describes how the pagination token returned will be the same as the input token when there are no more records to retrieve. Our pagination logic won't handle this case and will basically continue issuing subsequent API calls which yield empty responses for logs which are no longer actively appending.

Expected behavior

Other SDKs (e.g., Java v2, JS v3) have added customizations which handle GetLogEvents's non-standard pagination. We should investigate doing the same.

Current behavior

See above.

Steps to Reproduce

cloudWatchLogsClient
    .getLogEventsPaginated {
        logGroupName = "..."
        logStreamName = "..."
    }
    .collect { println("Page of log events: ${it.events?.size} records, nextToken = ${it.nextForwardToken}") }

Possible Solution

No response

Context

No response

AWS SDK for Kotlin version

1.2.28

Platform (JVM/JS/Native)

JVM

Operating system and version

any

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.