v3.1.1
If deploying v3.1.1 directly to your environment
Follow along the self-paced workshop for deployment and use case flow instructions
If upgrading from v3.1.0 to v3.1.1, please read below
If you have already deployed v3.1.0 to your environment, follow the below steps to update your deployment:
- Make a backup of config/env.yaml (or) a different configuration file if you are using a different name for your environment.
- Update your repository with the latest code from v3.1.1
- Overwrite the values specific to your environment in config/env.yaml with values from your backed up config/env.yaml
- Still at the root of the project, run
yarn cdk-synth-env
and validate that the synth is successful - Push the updated code to your repo using instructions from here
- This will automatically trigger the pipeline to deploy v3.1.1 to your environment
What's Changed
- Disable parallel builds triggering behaviour by CDK pipeline by @jmejco as the lag time for starting code build jobs across the 20 lambda asset bundling processes is nullifying the speed optimisation it's providing. Therefore, this behaviour is disabled which in turn provides the advantage that the account does not need non default concurrent code build runs quota.
Full Changelog: v3.1.0...v3.1.1