@giffels The current plan is to have the cobald.daemon.plugins.constraints define a (pydantic) schema for the entire plugin:

@plugin_constraints(required=True, schema=cobald_schema)
def load_pipeline(content: list):
    ...

It might be useful to allow schemas for yaml_constructors as well – that would make it easier to gradually add schemas "inside" a config, and free the plugin-wide schema from covering every case. Should I add it as well?

Closing this for the time being. With the current feature set, there isn't really any advantage over plugins just doing their own validation. Adding more meaningful features (e.g. precise configuration warnings) would be a too significant change right now.

This should be worth to revisit once the core library has been cleaned up and streamlined more.