Spring Cloud Config Compatibility problem for client if moving to new spring.config.import scheme (spring.cloud.config.profile not working)

I had an application working if I used the bootstrap additional dependency to work 'the old way'. Bootstrap properties was like this:

spring.cloud.config.uri=http://localhost:9000/
spring.application.name=config-client
spring.cloud.config.fail-fast=true
spring.cloud.config.label=master
spring.cloud.config.profile=dev

i then wanted to adopt the new scheme. I removed my bootstrap dependency and switched over to these app properties - only the first one really changing:

spring.config.import=configserver:http://localhost:9000
spring.cloud.config.fail-fast=true
spring.application.name=config-client
spring.cloud.config.label=master
spring.cloud.config.profile=dev
#spring.profiles.active=dev

But it no longer worked. It turned out that spring.cloud.config.profile didn't work, if I changed it to spring.profiles.active=dev it started working. Should it have worked without that change? The projects I'm tinkering with are in https://github.com/spring-projects-experimental/spring-graalvm-native/tree/master/spring-graalvm-native-samples/cloud-config - configclient is with bootstrap, configclient-new is without bootstrap (currently it is working with the change above made, but it can easily be flipped back) they will run (if ports align) against the configserver project in the same folder.