The wording of the client's settings override can be confusing and would be good to fix about spring-cloud-config

[ryanjbaxter]

That is basically the same as what we already say in the documentation

within the applications configuration coming from the config server

[ryanjbaxter]

No the key is the terms "applications configuration". This is referring to the the application's configuration being served up from the config server which is stored in Git, Vault, or any other environment repository.

[Junuu]

Thanks for the quick reflection!

[Junuu]

Does the term config server refer to an external repository like Git or Valut?

I think the yml configuration in Git or Valut etc is the remote configuration.

So I made the mistake of thinking of the Config Server term as the Spring Cloud Config Server and writing the Override property in that server's application.yml.

But in the end, I realized that I should have written the Override property in the application-local.yml of the Git repository.

This could be an error in translation as I don't speak English very well.

Thank you for your response.

[Junuu]

Thank you for your prompt response.

I appreciate your assistance in clarifying the documentation. Your explanation has certainly helped me understand the context better. However, I believe that the current wording might still be a bit confusing for others as well.

I suggest making the following change in the documentation:

as-is

If you enable config first bootstrap, you can allow client applications to override configuration from the config server by placing two properties within the applications configuration coming from the config server.

to-be

"If you enable config first bootstrap, you can allow client settings to override configuration from the config server by placing two properties within the applications configuration, which may include settings from external environment repositories such as Valut and Git."

If you find this suggestion reasonable, I would be more than happy to create a Pull Request to implement the proposed change. However, if you have any reservations or prefer an alternative approach, please feel free to discuss it further or close this issue accordingly.

Once again, thank you for your help and consideration.

Thank you.

[ryanjbaxter]

Thanks, I would just change the wording slightly...

If you enable config first bootstrap, you can allow client settings to override configuration from the config server by placing two properties within the applications configuration residing in the external environment repository(for example Git, Vault, SVN, etc) used by the config server.

How does that sound?

[Buzzardo]

I'd change that to:

If you enable config-first bootstrap, you can let client settings override configuration from the config server by placing two properties within the applications configuration that reside in the external environment repository (for example, Git, Vault, SVN, and others) used by the config server.

[ryanjbaxter]

Thanks @Buzzardo lets go with that!