Each time a new feature service layer is added in Kano we have to update the configuration if we'd like to distribute it. We should probably set a more automated rule as default behaviour, for instance automatically distribute all features services.
This will however require an update in https://github.com/kalisio/feathers-distributed as now only the service descriptor is available as input in the service configuration function. It should be better to also bind the function to the app so that more complex behaviour can be trigerred, eg get service object and check for a featureId option.
Each time a new feature service layer is added in Kano we have to update the configuration if we'd like to distribute it. We should probably set a more automated rule as default behaviour, for instance automatically distribute all features services.
This will however require an update in https://github.com/kalisio/feathers-distributed as now only the service descriptor is available as input in the service configuration function. It should be better to also bind the function to the app so that more complex behaviour can be trigerred, eg get service object and check for a
featureIdoption.