James Saryerwinnie

Should be pretty straightforward to plumb through the architecture config option, but we'll need to update the packager to handle binary python package dependencies. I'm not sure how many projects...

Not any particular reason other than no one's asked for them before. The [CHANGELOG](https://github.com/aws/chalice/blob/master/CHANGELOG.rst) has a list of changes for every release, and you install chalice via `pip` so there's...

Yeah the issue is that that null data source provides values that existing Chalice apps might be using in their existing tf templates so removing that provider would break their...

Thanks for the feature request, I agree this would be good to have.

Sounds like a great idea, might be worth just starting with the event configuration and handler API. We should be able to use Chalice's existing VPC config for Lambda functions.

Fixed via #1954

Hi, thanks for the pull request. Several of your examples mentioned filtering/processing of middleware based on the HTTP endpoint. For the REST API, was there an issue with accessing those...

Are you running the rerunning `chalice deploy` on the same machine? If you're using `chalice deploy`, chalice stores state about what it's deployed in a local `.chalice/deployed/*` directory. If that...

Looks like these are legitimate issues, we will need to figure out how to fix these before we can upgrade (might as as simple as implementing an empty `__attrs_attrs__` method...

I'm going to go ahead and close this. Looks like, there's a fix in attrs that will be part of the next release so I'd rather wait until that versions...