James Saryerwinnie

Thanks for the suggestion. Could you give a specific example of what types of things you would put in stage variables? What's an example of how you'd use an authorizer...

I'm interested to hear more, but I suspect this might be out of scope for chalice for now. Could someone suggest what the API/workflow would look like for an EC2...

Are you modifying of your `app.py` or other files in the meantime? It will restart the dev server whenever it detects you've made changes to your app.py. If you don't...

Ah so the issue is that it takes a while for the server to restart? Do you have any module level initialization in your app.py? How long does it take...

@Sytten are you also on windows? I've been trying to repro on my mac, perhaps it's something specific to windows.

Adding a parameter to `chalice deploy` should be pretty straightforward. Were you thinking something like this? ``` chalice deploy --config deploy-config.json ``` And `deploy-config.json` would look like: ``` {"lambda_arn": "arn:12345:..."}...

Can you give me more info on how to repro this issue? I tried the same steps you have here with the resource defined in the same order you've listed:...

Chalice currently requires AWS Lambda. I'm not sure I understand your use case. Are you using you want API gateway to use an EC2 as the backend instead of Lambda?...

> The best I found suggests using different profiles and then setting an AWS_PROFILE env var in the stage, but then the lambda that gets deployed cannot find such profile...

Just to make sure I understand what you're asking for, you'd prefer to set your region in your `.chalice/config.json` file, per stage? So something like this: ``` { "version": "2.0",...