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
dreamorosi opened this issue
Jul 24, 2023
· 2 comments
· Fixed by #1633
Assignees
Labels
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change tests
To run our integration (e2e) tests we deploy resources to an AWS account via CDK. These resources are spun up right before the test and then destroyed immediately afterwards. When we first wrote this infrastructure, CDK didn't allow programmatic use and so we had to rely on some workarounds. In the past months however CDK has released a new alpha module called @aws-cdk/cli-lib-alpha (link) that could potentially replace our workarounds.
We should look into this module and create an utility that can be used in all the tests that require AWS resources.
Why is this needed?
The current implementation relies on an internal CDK API. As such, its implementation can change at any time and break our test infrastructure. This has happened in one of the latest releases of CDK.
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.
The text was updated successfully, but these errors were encountered:
dreamorosi
added
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
confirmed
The scope is clear, ready for implementation
tests
PRs that add or change tests
labels
Jul 24, 2023
Comments on closed issues 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.
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change tests
Summary
To run our integration (e2e) tests we deploy resources to an AWS account via CDK. These resources are spun up right before the test and then destroyed immediately afterwards. When we first wrote this infrastructure, CDK didn't allow programmatic use and so we had to rely on some workarounds. In the past months however CDK has released a new alpha module called
@aws-cdk/cli-lib-alpha
(link) that could potentially replace our workarounds.We should look into this module and create an utility that can be used in all the tests that require AWS resources.
Why is this needed?
The current implementation relies on an internal CDK API. As such, its implementation can change at any time and break our test infrastructure. This has happened in one of the latest releases of CDK.
Which area does this relate to?
Tests
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: