It would be useful to permit the exclusion of a sink based on an incoming request's scope which could be defined by vendor, namespace, and version used in schema configuration. The current implementation will attempt to forward payload from requests to all configured sinks with deliveryRequired enabled. I propose a modification that would permit a list of exclusions for the sink.
Configuration in the config.yml for a sink would become something along the lines of:
An inclusion approach might also be appropriate. If include is not defined then make the sink applicable to all inputs (so as not to break current implementations), but if defined then only apply to specified filter.
It would be useful to permit the exclusion of a sink based on an incoming request's scope which could be defined by vendor, namespace, and version used in schema configuration. The current implementation will attempt to forward payload from requests to all configured sinks with deliveryRequired enabled. I propose a modification that would permit a list of exclusions for the sink.
Configuration in the config.yml for a sink would become something along the lines of:
An inclusion approach might also be appropriate. If include is not defined then make the sink applicable to all inputs (so as not to break current implementations), but if defined then only apply to specified filter.