-
Notifications
You must be signed in to change notification settings - Fork 372
AWS Parameter Store with Hoxton SR8+ doesn't override properties when using multiple profiles #772
Comments
@MatejNedic can you take a look at this one? We should fix it in both |
I think I experience the same issue with both (secretsmanager and the parameter store). In my case the least specific one always wins (eg. Do you need a sample project? I might can extend the sample project. Or can I help in some other way to solve this issue? Should I test the PR? EDIT: Woops, I thought I was in the new repo, there is an issue already open --> awspring/spring-cloud-aws#169 |
@WtfJoke You're correct the same issue exists with secrets manager too @maciejwalkowiak & @MatejNedic any chance of getting this merged in? |
I'm happy to create a separate PR for the secrets manager fix too if there is a appetite for this |
@peteguyatt the PR awspring/spring-cloud-aws#195 contains fixes for both (secrets manager and parameter store). Its probably better if we discuss in the new (migrated) issue 👍 |
@WtfJoke Thanks for porting the fix to the new repo and fixing secrets manager while you were at it, would you mind adding me as a contributor to the unit tests/PR in general? |
Type: Bug
Component:
Parameter Store
Describe the bug
When using multiple active profiles with spring cloud Hoxton SR10 and boot 2.3.9 we have noticed that property order seems to have changed, for example if we have two properties set E.g.
spring.profiles.active=profile_a,profile_b
Parameter Store configured as:
and in our bean we have
the value resolved will be abc-123 instead of efd-213
I looked through the commit history for
AwsParamStorePropertySourceLocator
and the issue seems to have been introduced in 582fdc6 where theCollections.reverse
has been removed due to switching to using aLinkedHashSet
This looks like an accidental bug to me and the same bug exists in master and the 2.3.x branch
The text was updated successfully, but these errors were encountered: