Spring cloud server doesn't load additional application.ymls by default anymore

[MAlberterLV1871]

Describe the bug
We have quite a few spring applications running in our kubernetes cluster and now we are trying to upgrade them to Spring version 4.3.1 (from 3.x.x).
All applications are partly configured by our spring cloud server which pulls serveal application.ymls from our git repository and we noticed beginning with release 4.3.1, application-{somename}.yml are not loaded by default anymore when booting up the spring cloud server hence we have to explicitly add {somename} to the list of profiles in the application.yml of the client to get full configuration otherwise the client doesn't boot because of unresolved values.
With all previous versions (last working 4.3.0) this works out of the box.
We assume this behaviour was introduced in Link and it heavily breaks our applications.
It would require us to update 100+ applications everytime we add a new profile to the clould config server
Is this intendend behaviour or is there a spring configuration option to disable it?

Sample
Cloud-Config-Server with 4.3.1

and with 4.3.0

Client with 4.3.1 Cloud Config still shows all active profiles though which is also quite missleading :

[ryanjbaxter]

Can you provide a complete, minimal, verifiable sample that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip file.

[MAlberterLV1871]

@ryanjbaxter Hi Ryan, i'm trying to create a minimal example which recreates the issue. From debugging our application it seems that if the config server gets queried with the default profile first by the client, the client stops resolving all the other profiles.
If it is a differnt profile it seems to work

[ryanjbaxter]

OK once we have a reproducer it will help make sure we are both on the same page and I can better assist

[spring-cloud-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-cloud-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.