Ask questionsAdd support for Secret Manager for RDS instance
When creating Secret for RDS with autorotate feature the secret is created in format:
From Micronaut perspective there's no way how to adjust the secret key name so it would respect the micronaut context path like
datasources.default.username so it would be automatically configured. The lambda function that handles the rotation expects exact format .
Because of this it would be great to have a way how to either: A) add the prefix for the properties before they are injected into context:
micronaut: config-client: enabled: true aws-secret-manager: - <secret-name>: prefix: datasources.default
B) Provide an datasource bean initialization handler very similar to  that based on secret name would do all the configuration for the user.
datasources: default: aws-secret-name: <secret-name>
 https://docs.aws.amazon.com/secretsmanager/latest/userguide/integrating_cloudformation.html  https://github.com/aws-samples/aws-secrets-manager-rotation-lambdas/blob/master/SecretsManagerRDSMySQLRotationSingleUser/lambda_function.py  https://github.com/micronaut-projects/micronaut-oracle-cloud/blob/master/oraclecloud-atp/src/main/java/io/micronaut/oraclecloud/atp/jdbc/hikari/HikariPoolConfigurationListener.java
Answer questions lightbody
Currently we're using the distributed configuration feature to keep our database password and OAuth client secrets out of the config files. But the way the AWS Secrets Manager distributed config is written, the secret must be in a specific pattern, such as:
In other words, the current integration asks you to store the secrets (name + kv pairs) in a Micronaut-friendly way. What you're asking for, given the rigidity of RDS's password rotation and secret storage solution, is for Micronaut to adapt to it rather than the other way around.
I would very much like support for this, or something like this :)
Related questionsNo questions were found.