Feature request: ability to set maxAge and decrypt via environment variables for Parameters

[mikebroberts]

Use case

I typically want to always set "decrypt" to true when getting parameters (since that works just fine whether an underlying SSM param is encrypted or not, and I'm accessing infrequently enough that costs and rate limiting is not a concern), and further I'd like to have a much longer default TTL for caching parameters so that I don't have to configure on every request.

Solution/User Experience

Be able to set env vars for default values for the parameters module, e.g. :

POWERTOOLS_PARAMETERS_TTL = 86400 (1 day)
POWERTOOLS_PARAMETERS_DECRYPT = true

(see also discussion in Discord at https://discordapp.com/channels/1006478942305263677/1088151329538580631/1088483265003925564)

Alternative solutions

No response

Acknowledgment

• This feature request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java, and .NET

Future readers

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

[dreamorosi]

Hi @mikebroberts, thank you for taking the time to open this feature request after our discussion on Discord.

Generally speaking I think this should be feasible and that it's a good feature to add. Before confirming and adding it to the backlog please allow me some time to look at the codebase and I'll get back to you here.

If confirmed, we'll have the feature in one of the next versions and before GA release.

[dreamorosi]

cc @heitorlessa, @jeromevdl - you might want to consider this feature too (omitting .NET for now since they don't have the utility yet).

[heitorlessa]

Leave with us! @rubenfonseca @leandrodamascena If I don't create an issue in the Python repo, please do - let's implement this, should be quite fast to do it.

[dreamorosi]

Just to follow up on this: I have opened a PR with the new env variables. They should be available in the next beta release or the one right after.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

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.