Chalice & Cognito custom scope using API Gateway generated invoke_url

Hello,

I'm trying to create a Chalice app that supports custom scope from Cognito via Terraform.

I was looking at this example: https://aws.github.io/chalice/topics/authorizers.html
It is great, but it assumes that scope name is known before the deployment.

For test/dev deployments, I would like to just use API Gateway generated uri.

API Gateway Deployment cannot be created without the swagger, but swagger needs to know API Gateway invoke url to generate proper custom scope.. Is there any way to solve this issue?

Start with the custom-scope authorizers example and the Terraform/API Gateway deployment flow described in the issue. Determine whether Chalice can support an invoke URL that is unavailable until after swagger generation. Done should be a clearly defined supported workflow or a documented reason the requested deployment sequence cannot be supported.

Written by the indexing model from the issue text.