Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
GetPipelineStateResponse doesn't serialize #517
I'm trying to move the scripts I'm using daily from calls-to-awscli-wrapped-in-Python to Haskell using Amazonka. So far it's been going smoothly, but now I've hit a possible bug.
I need to use
When I run
AFAICS this doesn't really match the documentation of the response that I found, but that might not mean much
I'm guessing that a possible fix would be to put in a few
I've seen this before in other AWS services and it rings the bell.
Notice the Required: Yes property. By not including it into the response they violate their own contract.
I believe that Amazonka's contracts are largely generated from the documentation (and it indeed generates
I don't know a good way of fixing it TBH. Definitely this bug should be raised with AWS support, but it may take time for them to fix an issue (or documentation), and the for Amazonka to reflect the change...
It doesn't surprise me that the blame falls on AWS, however that also makes me less hopeful for a proper fix arriving soon :(
With the size of the AWS API this sort of errors in the specification vs the implementation must have popped up before. Is there an established way to deal with it, ideally something better/quicker than "wait for Amazon to get their house in order"?
Alternatively, is there a way to "intercept" the response, to pick it up before de-serialisation?