Skip to content

S3 Backend Behaves Differently With Multiple Application Names #2642

@dmarmugi

Description

@dmarmugi

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 (Multiple spring application name for Vault #1356), this will return appB as propertySources[0] and appA as propertySources[1]
  • Against the S3 backend, this will return appA as propertySources[0] and appB as propertySources[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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions