Currently, the ordinal of the Spring Cloud Configuration values start at 450 (SpringCloudConfigClientConfigSourceFactory#76). This value is a bit high, according to the Quarkus documentation, System Properties have a ordinal of 400. With a ordinal of 450, Spring Cloud Configuration values cannot be overridden by existing configuration sources.
Implementation ideas
Like the extension quarkus-vault, it could be a good idea to let the developper to choose ordinal of the Spring Cloud Configuration sources.
Currently
int ordinal = 450;
// Profiles are looked from the highest ordinal to lowest, so we reverse the collection to build the source list
Collections.reverse(responses);
for (Response response : responses) {
/* ... */
Changes
int ordinal = config.ordinal();
// Profiles are looked from the highest ordinal to lowest, so we reverse the collection to build the source list
Collections.reverse(responses);
for (Response response : responses) {
/* ... */
config.ordinal() will be defined in SpringCloudConfigClientConfig with default value of 450.
Description
Currently, the ordinal of the Spring Cloud Configuration values start at 450 (SpringCloudConfigClientConfigSourceFactory#76). This value is a bit high, according to the Quarkus documentation, System Properties have a ordinal of 400. With a ordinal of 450, Spring Cloud Configuration values cannot be overridden by existing configuration sources.
Implementation ideas
Like the extension
quarkus-vault
, it could be a good idea to let the developper to choose ordinal of the Spring Cloud Configuration sources.Currently
Changes
config.ordinal()
will be defined inSpringCloudConfigClientConfig
with default value of 450.