Implemented an automatic deployment to a CDK stack called staging from all pushes to the develop branch. This will give us a testing backend environment, which will come in handy when trying share backend work with external partners before pushing to production, such as validating new datasets, for example.
I also removed the lambda package creation steps from the CircleCI config since that is now handled within the CDK deployment script
How I did it:
I moved the deploy job to deploy-production and created anther job deploy-staging which filters for the branch named develop.
I also removed the create lambda package step of the deploy job.
How you can test it:
Merge a small PR to develop and verify that the CDK staging stack gets updates (will update this PR with a comment containing the STACK URL once it get's deployed).
What I did:
Implemented an automatic deployment to a CDK stack called
stagingfrom all pushes to thedevelopbranch. This will give us a testing backend environment, which will come in handy when trying share backend work with external partners before pushing to production, such as validating new datasets, for example.I also removed the lambda package creation steps from the CircleCI config since that is now handled within the CDK deployment script
How I did it:
I moved the
deployjob todeploy-productionand created anther jobdeploy-stagingwhich filters for the branch nameddevelop.I also removed the
create lambda packagestep of thedeployjob.How you can test it:
Merge a small PR to develop and verify that the CDK staging stack gets updates (will update this PR with a comment containing the STACK URL once it get's deployed).