I think it'd be worth adding a GET version, fwiw. Could be the same handler
with just a different spelling maybe.
On Fri, Aug 20, 2021, 7:44 AM Mickael Maison <mickael.mai...@gmail.com>
wrote:
> Hi Chris,
>
> You're right, you can achieve the same functionality using the
> existing validate endpoint.
> In my mind it was only for validation once you have build a
> configuration but when used with an empty configuration, it basically
> serves the same purpose as the proposed new endpoint.
>
> I think it's a bit easier to use a GET endpoint but I don't think it
> really warrants a different endpoint.
>
> Thanks
>
> On Thu, Aug 19, 2021 at 2:56 PM Chris Egerton
> <chr...@confluent.io.invalid> wrote:
> >
> > Hi Mickael,
> >
> > I'm wondering about the use case here. The motivation section states that
> > "Connect does not provide a way to see what configurations a connector
> > requires. Instead users have to go look at the connector documentation or
> > in the worst case, look directly at the connector source code.", and that
> > with this KIP, "users will be able to discover the required
> configurations
> > for connectors installed in a Connect cluster" and "tools will be able to
> > generate wizards for configuring and starting connectors".
> >
> > Does the existing "PUT
> /connector-plugins/{connector-type}/config/validate"
> > endpoint not address these points? What will the newly-proposed endpoint
> > allow users to do that they will not already be able to do with the
> > existing endpoint?
> >
> > Cheers,
> >
> > Chris
> >
> > On Thu, Aug 19, 2021 at 9:20 AM Mickael Maison <mickael.mai...@gmail.com
> >
> > wrote:
> >
> > > Hi,
> > >
> > > I've created KIP-769 to expose connector configuration definitions in
> > > the Connect API
> > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-769%3A+Connect+API+to+retrieve+connector+configuration+definitions
> > >
> > > Please take a look and let me know if you have any feedback.
> > >
> > > Thanks
> > >
>
