James Saryerwinnie

This should be doable since the URL router should know what pattern it matched. Marking as a feature request.

You'll also need IAM access if you want chalice to create the roles/policies for you. I'll get the exact permissions documented.

This is a missing feature in Chalice. I think someone was initially going to work on this (https://github.com/aws/chalice/issues/1413) but I don't think that happened. I don't see a tracking issue...

Seems reasonable to me. Marking as a feature request.

Rebased/merged via 18ad456bae2a0b844c48810398a2fd95dde93cfc

I see what's happening here. Chalice is assuming it will always own the domain name, and that it's tied to a single rest api. So it will always create the...

Looks good, I'd just like to add a test for this in `tests/functinal/test_deployer.py` to make sure we don't regress on this functionality.

Is terraform complaining about circular dependencies? I haven't tried to set this up myself, but can you use a terraform variable for a scope value? e.g `scopes=["${aws_api_gateway_deployment.rest_api.invoke_url}/foobar.read"]`

After seeing the recent issues people were running into with the latest versions of terraform (#1717, #1869), I'm considering having some config option to generate a tf template that only...

The main thing is that the policy generation doesn't handle scoping the statements to the appropriate Resources, so providing your own policy file allows it to be more specific.