ConfigObserver should be adapted to the use case where the configuration is stored in a database like PostgreSQL. The PostgreSQL-specific support should probably not be built-in, but it should be adapted to the case where LISTEN-NOTIFY is used to get instant updates to all instances of a running application
This requires a refactoring of ConfigObserver and ConfigMap classes so that:
When a listener is requesting a configuration value, database value is preferred to file value which is preferred to environment
When something is changed in the database, we don't erroneously interpret all file-based values as having been removed
ConfigObserver should be adapted to the use case where the configuration is stored in a database like PostgreSQL. The PostgreSQL-specific support should probably not be built-in, but it should be adapted to the case where LISTEN-NOTIFY is used to get instant updates to all instances of a running application
This requires a refactoring of
ConfigObserverandConfigMapclasses so that: