You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To address scenarios where the Spring Cloud Config Server becomes unavailable (e.g., due to network issues or downtime), I propose adding an OnRemoteError callback or event mechanism to Spring Cloud Config Client. This feature would allow services to define their own fallback behavior, whether it is loading configuration from local files, databases, custom sources or implementing other context specific errorhandling related logic.
Note I am not suggesting you maintain any logic for loading the fallback properties directly. Instead, I am proposing an OnRemoteError callback or event that allows the services or projects to handle error management themselves and define their own fallback behavior.
event/callback should be made in such a phase as to allow the client to recover, using it's own choice of fallback property source
The text was updated successfully, but these errors were encountered:
improvement feature for errorhandling: related ticket: #1569
#1569
To address scenarios where the Spring Cloud Config Server becomes unavailable (e.g., due to network issues or downtime), I propose adding an OnRemoteError callback or event mechanism to Spring Cloud Config Client. This feature would allow services to define their own fallback behavior, whether it is loading configuration from local files, databases, custom sources or implementing other context specific errorhandling related logic.
Note I am not suggesting you maintain any logic for loading the fallback properties directly. Instead, I am proposing an OnRemoteError callback or event that allows the services or projects to handle error management themselves and define their own fallback behavior.
event/callback should be made in such a phase as to allow the client to recover, using it's own choice of fallback property source
The text was updated successfully, but these errors were encountered: