Maintenance: adopt AppConfig L2 constructs in Parameters integration tests #2396
Closed
1 of 2 tasks
Labels
completed
This item is complete and has been merged/shipped
good-first-issue
Something that is suitable for those who want to start contributing
tests
PRs that add or change tests
Summary
AWS CDK has added L2 constructs for AWS AppConfig that allow to create AppConfig resources more easily.
The AppConfig Provider part of the Parameters utility uses L1 constructs that are more verbose and require explicit management of dependencies between entities.
We should replace the existing construct with the newer.
Why is this needed?
So that the integration tests for the Parameters utility can become a little less verbose and less brittle.
Which area does this relate to?
Tests
Solution
Replace the code found here with the L2 constructs.
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: