Currently, whenever we tear down the CloudFormation stack and reploy with the CDK, the new API Gateway creates a new ID that is used in the URLs for the dev server to talk to (such as https://oe6vezgey6.execute-api.us-east-1.amazonaws.com/, the ID is oe6vezgey6), and currently, we have to copy and paste this ID from the AWS console into frontend/src/AppConstants.tsx. This is annoying, and it would be nicer if dev stack deployments could always set up the API Gateway to have the same URL, so we wouldn't have to update this ID every time.
A cursory look into this issue seems to suggest this would entail associating a domain name certificate with the API Gateway, which would probably mean using AWS Certificate Manager, and maybe talking to Russell to get the domain name info.
One other (janky) idea is also to just write a script (perhaps called from backend/app.py?) that would manually open frontend/AppConstants.tsx and write the ID to the variable.
Currently, whenever we tear down the CloudFormation stack and reploy with the CDK, the new API Gateway creates a new ID that is used in the URLs for the dev server to talk to (such as
https://oe6vezgey6.execute-api.us-east-1.amazonaws.com/
, the ID isoe6vezgey6
), and currently, we have to copy and paste this ID from the AWS console intofrontend/src/AppConstants.tsx
. This is annoying, and it would be nicer if dev stack deployments could always set up the API Gateway to have the same URL, so we wouldn't have to update this ID every time.A cursory look into this issue seems to suggest this would entail associating a domain name certificate with the API Gateway, which would probably mean using AWS Certificate Manager, and maybe talking to Russell to get the domain name info.
One other (janky) idea is also to just write a script (perhaps called from
backend/app.py
?) that would manually openfrontend/AppConstants.tsx
and write the ID to the variable.