Improper precedence between property in global section of application.yml and global section of foo.yml

I am using config server against a git repository. This git repostiory has two files, application.yml and foo.yml (my app is named foo).
example:

application.yml

myglobalsectionwithwhateverelse
---
spring.config.activate.on-profile: myprofile
myproperty: value1

foo.yml

myproperty: value2
---
spring.config.activate.on-profile: myprofile
... other properties

The property being resolved in my application when i use profile myprofile is value1, where I would expect it to be value2. This is because any properties in the app specific yaml should be more important.

I am using spring cloud starter config version 4.3.2

Reproduce the precedence issue in the config server using application.yml and foo.yml with the myprofile profile and the two conflicting myproperty values. Trace how the global and application-specific sections are resolved, then verify that foo.yml supplies the effective value for the profile.