intermediateCentralized Configuration: Config Server & Config Client
Why does changing a value in Config Server's Git repo not immediately affect already-running service instances?
Config Server only serves configuration to services on their next startup by default — already-running instances already fetched their config and won't re-fetch it automatically, which is exactly why @RefreshScope and a manual or Config-Bus-triggered refresh exist.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response