endgame
endgame
About time I gave another update. Amazonka now has bindings to every service in botocore except for two (`s3control` and `lexv2-runtime`). In a couple of weeks I should get another...
[The Milestone](https://github.com/brendanhay/amazonka/milestone/3) is pretty up-to-date, so if you have time I would recommend trying to pick things off from that. #689, #638, #754, and #810 are all pretty routine. #745...
For something like S3, exponential backoff should be fine with the tools in the `Retry` type: https://github.com/brendanhay/amazonka/blob/5ad346c554ad370e9164393c70f73a8d21956a38/amazonka/src/Network/AWS/Types.hs#L398-L406 The problem with dynamodb here is that you get a _successful_ response that...
This sounds to me like both the following are true: * Localstack is wrong. * We should be parsing entities into a single character This is low-enough priority that it...
Another use case for request/response hooks: rewriting requests for non-S3 object stores. See #760.
If the Go SDK is to be believed, iterating until an empty response is [not safe](https://docs.aws.amazon.com/sdk-for-go/api/service/cloudwatchlogs/#CloudWatchLogs.GetLogEvents): > This operation can return empty results while there are more log events available...
That paginator does not generate good code for amazonka: it tries to stop if `nextForwardToken` is `Nothing`, but the API will return the token it was given if there's nothing...
Given that it's not in botocore and I suspect the java pager will likely try to page indefinitely also, I think there's an argument for just closing this issue. But...
I am against a solution which excludes GHC >=8.8 && Type` in your records, and substituting `Proxy` or `Identity`. This may be a bit confusing for readers unfamiliar with the...
> As mentioned in the opening - treat this as documentation of exploratory work. There is no intention to push a particular approach within any foreseeable release window(s). That's cool....