Open arielvalentin opened 10 months ago
cc @djaglowski
This problem is not specific to connectors. The validate command currently does not consider supported data types for any class of component.
That said, I agree there are additional configuration errors, such as this one, which we could surface within the command if we would try to instantiate (but not start) a service.
I raised this in #8866 after missing this issue in a search (somehow).
As I noted in that issue, it'd also be extremely helpful if the connector error mentioned the specific pipeline name in its complaint, e.g logs/out
instead of just logs
, like this:
Error: failed to build pipelines: connector "forward/test" used as receiver in "logs/out" pipeline but not used in any supported exporter pipeline
Currently it doesn't name the actual pipeline, so in complex configurations it can be tricky to tell what exactly it's complaining about.
Is your feature request related to a problem? Please describe.
I expected the configuration validator to find pipeline issues related to invalid usage of connector components, however the collector fails to start due to invalid usage and exits.
Here is an example that defines a
count
connector and uses it as a receiver in a metrics pipeline:The config.yaml passes validation:
However upon using this configuration, the collector reports an error and exits:
 Describe the solution you'd like
I expect the validator to return an error