renaming resource key results in error about aws-api-gateway-for-cloudformation HOT 6 CLOSED

I'll have to look at that. Can you send me a template example?
On ons 9 mars 2016 at 21:39, Bryan [email protected] wrote:

When renaming a variable path part the new one gets added before the old
one is deleted

e.g.
/resource1/{key}
renamed to
/resource1/{key1}

BadRequestException: Resource with id 'null' has more than one variable
component as a direct child: [{key}, {key1}]

—
Reply to this email directly or view it on GitHub
#18
.

from aws-api-gateway-for-cloudformation.

I just had a quick look, are you updating a Resource or a Method?

When resources are updated I call updateResource. If there is an issue there you've stumbled across a bug in API Gateway.
When methods are updated, the old method is deleted and a new method is created in its place. If there is a problem here, I guess again we've come across an interesting "feature" in API Gateway.

This is fairly interesting too:

aws apigateway update-resource --rest-api-id abc123 --resource-id abc456 --patch-operations op=replace,path=/pathPart,value={test1}

Error parsing parameter '--patch-operations': Expected: ',', received: '}' for input:
op=replace,path=/pathPart,value={test1}
^

aws apigateway update-resource --rest-api-id abc123 --resource-id abc456 --patch-operations op=replace,path=/pathPart,value="test2"
{
"path": "/test/test2",
"pathPart": "test2",
"id": "abc456",
"parentId": "abc456789"
}

from aws-api-gateway-for-cloudformation.

Interesting!

from aws-api-gateway-for-cloudformation.

I just had a quick look, are you updating a Resource or a Method?

A resource

e.g.
/resource1/{key}
renamed to
/resource1/{key1}

from aws-api-gateway-for-cloudformation.

Can we close this as an AWS bug or do you have more information for me?

from aws-api-gateway-for-cloudformation.

Ok to close?
I have reported this to AWS.

from aws-api-gateway-for-cloudformation.