Skip to content
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

aws ec2 replace-route: The parameter destinationCidrBlock is not recognized #13

Closed
jdub opened this issue Dec 27, 2012 · 2 comments
Closed
Milestone

Comments

@jdub
Copy link

jdub commented Dec 27, 2012

This isn't a camelCase vs. InitialCamelCase issue, is it? :-)

http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-ReplaceRoute.html

$ aws ec2 --region ap-southeast-2 replace-route --route-table-id rtb-e87a9681 --destination-cidr-block 0.0.0.0/0 --instance-id i-d97a36e3 
{
    "Response": {
        "Errors": {
            "Error": {
                "Message": "The parameter destinationCidrBlock is not recognized", 
                "Code": "UnknownParameter"
            }
        }, 
        "RequestID": "1603aba7-40aa-4c2c-aa50-5fc7c6faa032"
    }
}
A client error (UnknownParameter) occurred: The parameter destinationCidrBlock is not recognized
@jdub
Copy link
Author

jdub commented Dec 27, 2012

Adding --debug indicates that camelCase parameters are used, rather than InitialCamelCase.

@garnaat
Copy link
Contributor

garnaat commented Dec 27, 2012

This should be fixed in boto/botocore@22d0db0

@garnaat garnaat closed this as completed Dec 27, 2012
kdaily referenced this issue in kdaily/aws-cli Apr 15, 2021
Wrap task submission for transfer into tasks
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
Fixing debug log print when checking package version. Fixes aws#11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants