Right now, we check against the current stage to determine whether or not to use a custom domain. Unfortunately, both our dev & production environment are named in the dev stage (by the STAGE tag in the Lambda function and the "Stages" config in API Gateway... perhaps elsewhere too).
For now, we can deploy by hacking serverless.yml before a prod deploy:
Right now, we check against the current stage to determine whether or not to use a custom domain. Unfortunately, both our dev & production environment are named in the
dev
stage (by theSTAGE
tag in the Lambda function and the "Stages" config in API Gateway... perhaps elsewhere too).For now, we can deploy by hacking
serverless.yml
before a prod deploy:Then it's just
sls --aws-profile serverless-production deploy
(using the production access ID and secret key stored in Lastpass).