Maintenance: Migrate to CDK CLI and off Docker for E2E tests

[heitorlessa]

Summary

This tracks the work necessary to use CDK CLI for synthesizing and deploying E2E stacks in parallel. It also tracks our initial move away from Docker to build Lambda Layer, as it slows down E2E authoring significantly (~1.3m) for every individual run.

Why is this needed?

For v2, @rubenfonseca needed to use the default VPC for Event Handler E2E test. We were caught by surprise that CDK Context Lookup methods only work via CDK CLI, which invalidates our initial implementation.

Which area does this relate to?

Tests

Solution

PR incoming. We've successfully moved to use CDK CLI while keeping our authoring and parallel deployment experience.

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 1.30.0 version!