S3 Backend Behaves Differently With Multiple Application Names
dmarmugi opened this issue · 1 comments
dmarmugi commented
Describe the bug
Given
- Spring Cloud Config Server Version 4.1.3
spring.application.name: appA,appB
spring.profiles.active: dummy
When
- Resulting Request:
http://<config server>/appA,appB/dummy
(the profile name doesn't matter here, just the app names)
Then
- Against Git and Vault backends (#1356), this will return
appB
aspropertySources[0]
andappA
aspropertySources[1]
- Against the S3 backend, this will return
appA
aspropertySources[0]
andappB
aspropertySources[1]
This is a problem because:
This affects the override behavior in cases where the same value exists in both appA
and appB
's responses
dmarmugi commented
Searching with regex for \.findOne\("\w+,\w+
turned up these tests:
Vault and Spring Vault have tests asserting precedence:
So, too, CredHub:
Unfortunately, AWSS3 and Git seem to just assert on size of response: