Open
Description
Would anyone use a EnvVarProcessor that uses the AWS Secrets Manager?
What I'm thinking is to implement EnvVarProcessorInterface and create a awsSecret key that takes a SecretId, and optionally a versionID and / or versionStage and resolves this in runtime. Then in config, you can use a string similar to this to use amazon secrets in the config.
parameters:
db_dsn: "mysql://db_user:%env(awsSecret:db_password)%@127.0.0.1:3306/db_name"
Thoughts? Does anyone want this? Would such a feature be merged?