Maintenance: adopt AppConfig L2 constructs in Parameters integration tests

[dreamorosi]

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

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

[daschaa]

I would like to take this issue ❤️

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