endgame
endgame
In amazonka-schedule, the client Tokens are not autogenerated while creating /updating new schedules
Can you explain a bit more about what you mean here? According to that documentation, and the [most recent AWS API docs](https://docs.aws.amazon.com/scheduler/latest/APIReference/API_CreateSchedule.html#scheduler-CreateSchedule-request-ClientToken), that field is optional and the API will...
Because of #888, we are stuck on botocore revision `f14ab129706a99198d42eed78d75350ea61c48e9`, which doesn't define that field. Fixing the generator and getting all of this right therefore cannot happen until 2.2.
@nitinprakash96 you may want to subscribe to this.
Blocked by #888
Absolutely. Can users of older GHCs get `containers >=0.8` i.e., should we consider a metadata revision too?
OK, thanks. I'll move this issue to 2.2 and we'll do 0.7 compat as part of 2.1.
Taggings are encoded as query parameters. I recently fixed a bug with request signing of query parameters; can you check latest `main` and see if this is still an issue?...
As Hackage Trustee (`jack`), I have made the following revision to `hspec-golden-0.2.2.0`: * On component `hgold`: `optparse-applicative >=0.18.1 && `>=0.18.1 &&