fix(parameters): AppConfigProvider when retrieving multiple unique configuration names

[leandrodamascena]

Issue number: #2362

Summary

Changes

This RP aims to fix the issue with the AppConfig parameter provider retrieving different parameters in the same Lambda execution. The way it is implemented, self._next_token caches token globally and retrieves only the value of the first call, and discards the others.

User experience

from typing import Any

import requests

from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities import parameters
from aws_lambda_powertools.utilities.typing import LambdaContext

logger = Logger()

def lambda_handler(event: dict, context: LambdaContext):
    endpoint_comments_config: Any = parameters.get_app_config(name="config", environment="dev", application="comments", max_age=0)
    
    endpoint_comments_features: Any = parameters.get_app_config(name="features", environment="dev", application="comments", max_age=0)

    logger.info(endpoint_comments_config)
    logger.info(endpoint_comments_features) # <- THIS will print the value of name="config" instead of name="features"

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[heitorlessa]

nicely done @leandrodamascena <3

https://media.giphy.com/media/mbhseRYedlG5W/giphy.gif