Define generic service interface for a generic form based UI to create/configure Event Sources

[chirino]

With #702 you can machine discover available event sources. Would be nice if that could be extended so that a machine could create those Event source CRDs too. Basically thinking you could have a service which can drive a generic form builder type UI.

Once you have a fully configured/validated set of form fields, the service gives you back the CRD for that event source. This could be used by a generic UI to drive configuring 3rd party event sources that it never knew about.

[chirino]

If you guys think something like this is in scope for this eventing working group, we could extract and contribute an interface that's similar that we have been using in the Syndesis project that allows 3rd party UI driven configuration of event sources.

[evankanderson]

/area ux-discussion

I think this is an interesting area for exploration... could you do a short proposal/presentation for the 2/27 eventing WG meeting?

[chirino]

Sure. I'll also try to extract the gist of API interface into an openapi document so it can be shared at the meeting.

[chirino]

Initial pass at extracting that api is at: https://app.swaggerhub.com/apis/chirino/event-source-config/1.0.0?loggedInWithGitHub=true#/default/validate

[derberg]

hey, just curious question as in Kyma we have some experience in rendering specs, like https://asyncapi.com/asyncapi-react/ or the JSON Schemas of information passed as part of https://www.openservicebrokerapi.org/ (where we use https://github.com/mozilla-services/react-jsonschema-form)

looking on your example, do I get it right, that you suggest it makes sense to use openapi for events registry?

[chirino]

react-jsonschema-form seems really interesting, if we standardize on that, then we can further reduce the complexity of the proposed example.

Basically, if we could provide both the jsonschema and an optional UISchema for an event source, we should be 80% of the way there. Both those should be static to the source, so perhaps we just annotate the Event Source CRD with those schemas.

The only features that api covers that would not be cover are:

• Dynamic options for fields accessed from online system.
• Conditionally showing fields based on field values
• Multipage configs.

So for that last 20% perhaps we can come up with a simpler optional API which can supplement that info.

[epicfaace]

@chirino FYI, react-jsonschema-form does have the "conditionally showing fields based on field values" functionality, see https://react-jsonschema-form.readthedocs.io/en/latest/dependencies/#dynamic

[akashrv]

/kind feature-request

[n3wscott]

This might be what the Discovery API is also trying to help with.

[akashrv]

@nachocano

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.