Replies: 3 comments
-
Parameter Store and Secrets Manager integrations cannot be customized in the same way as other integrations because they are created in the bootstrap phase. Take a look at this issue to see how this can be done: #205 |
Beta Was this translation helpful? Give feedback.
-
@maciejwalkowiak thanks for the hint
what seems the most probable option for the class, is: |
Beta Was this translation helpful? Give feedback.
-
Is there a solution to this? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Type: Feature
Component:
Parameter Store
Is your feature request related to a problem? Please describe.
I'm using java 11 => stick to 2.x version.
Based on official docs, following are the ways to provide credentials:
https://cloud.spring.io/spring-cloud-static/spring-cloud-aws/2.2.0.M2/reference/html/#_sdk_credentials_configuration
As I'm running with localstack => accessKeyId and secretAccessKey vals are irrelevant, still I'm forced to provide any value, otherwise the
Describe the solution you'd like
For the local run profile, I'd like to use
application_<profilename>.properties
to provide credentials. Currently whatever properties I tried didn't work, e.g.:(referred in the docs: https://cloud.spring.io/spring-cloud-static/spring-cloud-aws/2.2.0.M2/reference/html/#_configuring_credentials) are ignored.
And result is:
Describe alternatives you've considered
I'd love to see what keys in the
application_<profilename>.properties
are about to be used, to be later propagated to authorization call.My current workaround is to set the system properties very early manually:
META-INF/spring.factories
:Which doesn't however sound right.
Beta Was this translation helpful? Give feedback.
All reactions