v3.1.2

If deploying v3.1.2 directly to your environment

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

If upgrading from v3.1.1 to v3.1.2, please read below

If you have already deployed v3.1.1 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.2
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 cdk-synth-env and validate that the synth is successful
5. Push the updated code to your repo using instructions from here
6. This will automatically trigger the pipeline to deploy v3.1.2 to your environment

What's Changed

• Update state machine behaviour for current configuration discovery, region switch and version upgrade to fail gracefully where feasible. This would ensure that when there are multiple entities being processed, the state machines would not fail if one entity processing failed. Instead, the error details are written to logs and the execution continues.
• Instances where the state machines for the scenarios described above throw errors are:
  - When there's an exception for triggering the state machine logic i.e. input cannot be retrieved
  - Any failure (of any type) in region switch deploy triggers a failure. This is by design to ensure that when the state machines trigger a write operation, even a single error rolls back the entire configuration.
• Add troubleshooting document that explains the logging convention , different cloud watch log groups and insights queries set up by the solution

Full Changelog: v3.1.1...v3.1.2