Maintenance: update output generation for e2e

[dreamorosi]

Summary

The experimental CDK toolkit CLI that we use for our e2e tests has introduced a lock mechanism on the output folder generated by a stack being synthesized.

This conflicts with our current usage that creates a shared folder and generates test-specific output files, thus causing the tests to fail.

Why is this needed?

So that the e2e tests can continue working with the newer version of the experimental CDK toolkit.

Which area does this relate to?

No response

Solution

Update the logic that generates the output folder to be unique for each test.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[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 v2.19.0 version!