Skip to content

v3.1.8

Latest
Latest
Compare
Choose a tag to compare
@jmejco jmejco released this 10 Jan 09:58
· 4 commits to main since this release
v3.1.8
f369ece
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

If deploying v3.1.8 directly to your environment

Follow along the self-paced workshop for deployment and use case flow instructions

If upgrading from v3.1.7 or older to v3.1.8, please read below

If you have already deployed an older version to your environment, follow the below steps to update your deployment:

  1. Make a backup of config/env.yaml (or) a different configuration file if you are using a different name for your environment.
  2. Update your repository with the latest code from v3.1.8
  3. Overwrite the values specific to your environment in config/env.yaml with values from your backed up config/env.yaml
  4. Still at the root of the project, run yarn install --frozen-lock-file to install the new dev dependencies introduced in this release
  5. Still at the root of the project, run yarn cdk-synth-env and validate that the synth is successful
  6. Push the updated code to your repo using instructions from here
  7. This will automatically trigger the pipeline to deploy v3.1.8 to your environment

What's Changed

  • Handle duplicate custom lambda layer version name issue
  • Handle null exception when managed policies in permission set go from empty to with values array (or) vice-versa
  • For detailed descriptions of these changes, see #109

Full Changelog: v3.1.7...v3.1.8

Assets 2
Loading