Discussion thread: here
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Kafka Connect provides a REST interface for managing connectors. Below is a list of supported documented endpoints:
In addition to above methods, OPTIONS method could be also used.
Response to OPTIONS request includes auto-generated WADL, e.g.:
Having WADL is useful for code generation, applications modeling and visualizations, etc. At the same time, it might also be a security threat.
So users should have a way to disable exposing WADL via Connect REST endpoints.
Add a new Kafka Connect Distributed/Standalone worker configuration property to enable/disable exposure of WADL via Connect REST endpoints.
Add configuration parameter:
- rest.wadl.enable with the default value of 'true', and with the importance of 'low'.
Update org.apache.kafka.connect.runtime.rest.RestServer to respect the configuration property described above.
With rest.wadl.enable=true, response to OPTIONS method should have list of supported HTTP methods only, e.g.:
Add more unit tests under org.apache.kafka.connect.runtime.rest.RestServerTest, asserting on response's Content-type.
Compatibility, Deprecation, and Migration Plan
Since the default value of the new configuration parameter is 'true', the change should be backward compatible, no action is required for upgrading from older versions.
- Disable exposure of WADL without an option to keep exposing it. Some users might rely upon it.