How much configurability a software requires, and how much hardcoding of such parameters is acceptable depends highly on the way how the software will be operationally used.

For example, do you expect a potential need to change endpoints during your holidays? Then make them configurable, so operations don't have to ask you to change the libraries during your vacation. Maybe a simple configuration file per lib or service is enough, you have to decide this by yourself.

Or do you expect the requirement to change the same endpoint shared by a dozen services, simultanously, for keeping the downtime next to zero during operation? Then a centralized service would start making sense, otherwise it looks pretty overengineered to me.

So clarify your goals! Configurability is not an end in itself, it is a means to an end.

How much configurability a software requires, and how much hardcoding of such parameters is acceptable depends highly on the way how the software will be operationally used.

For example, do you expect a potential need to change endpoints during your holidays? Then make them configurable, so operations don't have to ask you to change the libraries during your vacation. Maybe a simple configuration file per lib or service is enough, you have to work this out with the colleagues from operations.

Or do you expect the requirement to change the same endpoint shared by a dozen services, simultanously, for keeping the downtime next to zero during operation? Then a centralized service would start making sense, otherwise it looks pretty overengineered to me.

So clarify your goals! Configurability is not an end in itself, it is a means to an end.