Skip to content

feat(lambda-layer): add pipeline to build Lambda layer in v3 #4826

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Jul 30, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Addressing Heitor's feedback
  • Loading branch information
leandrodamascena committed Jul 29, 2024
commit 1f827064f3e0e5dbd651e1e6306e53d5ea19fcfe
15 changes: 4 additions & 11 deletions docs/automation.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,22 +87,15 @@ This is a snapshot of our automated checks at a glance.

![Continuous Deployment practices](./media/continuous_deployment_practices.png)

## Lambda layer build & deploy
## Lambda layer pipeline

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.

<!--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.-->

Next, we deploy these CDK Assets to the beta account across all AWS regions. Once the beta deployment is complete, we execute the following:
Next, we deploy these CDK Assets to the beta account across all AWS regions. Once the beta deployment is complete, we run:

* **Canary Tests**: Run thorough canary tests to assess stability and functionality
* **In case of success**: If canary tests pass, deploy previous CDK Asset to production across all regions
* **In case of error**: If any canary tests fail, halt pipeline to investigate and remediate issues before redeploying

This process ensures the quality of the delivery and helps anticipate problems to avoid impacting customers.

<!--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.
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. -->
* **Successful?**: Deploy previous CDK Asset to production across all regions
* **Failure?**: Halt pipeline to investigate and remediate issues before redeploying

```mermaid
graph LR
Expand Down
Loading