-
Notifications
You must be signed in to change notification settings - Fork 90
Different behavior while using SSMProvider #758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jeromevdl Would you have some bandwidth to look into this issue ? Look like a bug to me. |
Thanks @dmahapatro for this issue. I think it's an issue in the Java SDK because we're just using the standard builder:
Using the AWS CLI, both with and without trailing slash work, but not with the Java SDK. We can probably remove the trailing slash if there is one. |
remove trailing slash for multiple params
remove trailing slash for multiple params
This is now released under 1.12.0 version! |
I have stored
/DEV/APP/CLIENT/KEYSTORE/PASSWORD
and/DEV/APP/CLIENT/TRUSTSTORE/PASSWORD
in SSM Param Store, with secure strings as value.I am retrieving them in Lambda function as:
Expected Behavior
The expected behavior is that the keys as shown above
KEYSTORE/PASSWORD
andTRUSTSTORE/PASSWORD
should be presentCurrent Behavior
While debugging, I found the keys to be as
KEYSTOREPASSWORD
andTRUSTSTOREPASSWORD
.However, if I remove the appending
/
from the path and use/DEV/APP/CLIENT
:I get the expected results
Steps to Reproduce (for bugs)
Just ran a Test class with a main method inside a Maven project:
Environment
null
value afterget()
operation on MapThe text was updated successfully, but these errors were encountered: