-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apigateway::put-integration
command results in KeyError: u'http_method'
#1595
Comments
Interesting. Looks like |
It looks like this is a bug in our model for API Gateway, which is generated upstream. I'll update the ticket when a fix is in the pipes. |
I am seeing the same problem. I can put a method, but then I am stuck putting an integration so I have to do that via the web. |
Any update on this? I have a bunch of deployment stuff to do and right now my only option is to do a create-resource, put-method and put-method-response for each node and http-method, but then I have to go into the web interface to do all what should be covered in the put-integration call. That goes across a couple of different pages in the UI and I have to do it for all 4 http methods. This bug is the one thing between me and fully scripted goodness. |
We had a bug in our models that we get upstream, it will be fixed in the next release. |
I installed the developer branch and the code that should be working is giving me the following error now: A client error (BadRequestException) occurred when calling the PutIntegration operation: Enumeration value for HttpMethod must be non-empty It think there is a typo somewhere in that "HttpMethod" should be "httpMethod" because that's the parameter that the CLI is expecting. If have tried using the regular command-line method as well as the --cli-input-json format and the error is the same. |
API http://docs.aws.amazon.com/cli/latest/reference/apigateway/put-integration.html
There's no example code in the documentation, so my usage might be wrong. Anyway, this error occurs in client-side(AWS-CLI) before requesting to the server.
The text was updated successfully, but these errors were encountered: