You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We fetch the latest PyPi release, then build Python **3.8-3.12** for **x86_64** and **arm64** architectures, using QEMU emulation for arm64. We create **a single CDK Asset** with x86_64 and arm for each Python version to optimize deployment performance.
93
93
94
-
<!--In our layer deployment pipeline, we begin by fetching the **latest PyPi release**. After that, we build Python versions 3.8, 3.9, 3.10, 3.11, and 3.12 for both x86_64 and arm64 architectures. For the arm64 builds, we utilize QEMU emulation to ensure compatibility. After completing the builds, we create **a single CDK Asset** containing both Stacks for each Python version. This approach is adopted to optimize performance during the deployment process.-->
95
-
96
-
Next, we deploy these CDK Assets to the beta account across all AWS regions. Once the beta deployment is complete, we execute the following:
94
+
Next, we deploy these CDK Assets to the beta account across all AWS regions. Once the beta deployment is complete, we run:
97
95
98
96
***Canary Tests**: Run thorough canary tests to assess stability and functionality
99
-
***In case of success**: If canary tests pass, deploy previous CDK Asset to production across all regions
100
-
***In case of error**: If any canary tests fail, halt pipeline to investigate and remediate issues before redeploying
101
-
102
-
This process ensures the quality of the delivery and helps anticipate problems to avoid impacting customers.
103
-
104
-
<!--Next, we deploy these CDK Assets to the beta account across all AWS regions. Once the deployment in the beta account is complete, we execute canary tests. These tests cover all platforms, runtimes, and regions, allowing us to thoroughly assess the stability and functionality of the deployment. If the canary tests are successful, indicating that the deployment meets our quality standards, we proceed to deploy the previous CDK Asset to the production account. This deployment is rolled out across all AWS regions, ensuring widespread availability of the latest version and keeping previous version untouched.
105
-
However, if any of the canary tests fail, indicating potential issues with the deployment, we halt the pipeline immediately. This preventive measure allows us to investigate and remediate any problems before attempting another deployment. -->
97
+
***Successful?**: Deploy previous CDK Asset to production across all regions
98
+
***Failure?**: Halt pipeline to investigate and remediate issues before redeploying
0 commit comments