According to the docs here config-server should not serve its own application.properties
(or yml presumably) to clients, even if native
profile is active.
It seems that Ilford config-server has a regression on this point.
I've attached sample config-server and config-client apps. The client fails to start when the server is running as it tries to use the server.port
set in the server's application.yml.
This is blocking the spring-cloud-services tile upgrade to boot 2.4 and Ilford as we use the native profile when a config-server is created with no explicit backing config repo. Without this, a user can't create an empty config-server and update it afterwards with backing config.