Very interesting. Would the proposed configuration provider be set at the connector level or the worker level? The latter would obviously be required to handle all/multiple connector configurations. Either way, the provider class(es) would need to be installed on the worker (really, every worker), correct?
Would all provider implementations be custom implementations, or are there some provider implementations that are general enough for Connect to include them? Best regards, Randall On Fri, Oct 20, 2017 at 5:08 AM, Florian Hussonnois <fhussonn...@gmail.com> wrote: > Hi Team > > Before submitting a new KIP I would like to open the discussion regarding > an enhancement of Kafka Connect. > > Currently, the only way to configure a connector (in distributed mode) is > through REST endpoints while creating or updating a connector. > > It would be nice to have the possibility to specify a configs provider > class (as we specify the connector class) in the JSON payload sent over the > REST API. > This class would be called during the connector creation to complete the > configs submitted via REST. > > The motivations for a such functionality is for example to enforce a > configuration for all deployed connectors, to provide default configs or to > provide sensitive configs like user/password. > > I've met these requirements on different projects. > > Do you think, this feature merits a new KIP ? > > Thanks, > > -- > Florian HUSSONNOIS >
