Replies: 1 comment
-
@Cimballi you're welcome to submit a PR to update docs |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I recently migrated a project from Spring Cloud AWS v2.x to v3.x and I am facing a problem with @value.
In the logs I can see :
"Populating property retrieved from AWS Parameter Store: .x.y.z"
But then later :
Could not resolve placeholder 'x.y.z' in value "${x.y.z}
Other properties, like Spring properties for the database configuration for example, are working fine.
So could it be a bug with @value ?
Edit: The problem may not be with @value but with SpEL because the following is not working neither :
@SqsListener(value = {
"${x.y.z}"
})
Edit: It may be related to a missing "/" at the end of the config import, as mentioned in #696, I am going to give it a try.
Edit: I confirm it solved the problem. So, a couple of comments, first it's strange that it's working fine for Spring properties but not for custom properties, second there should be a clear comment about that point in the documentation. Thanks !
Beta Was this translation helpful? Give feedback.
All reactions