events

I have this implemented in a custom marshaler now but wondering if it makes sense to push back upstream - when we are integrating with legacy services we find it useful to use the correlation ID as the message ID when first brought into watermill - from there they get sent on headers to subsequent services and work normally.

Its a simple change if it would make sense for other users.

Problem

Sugar Controller is a separate install, which makes its functionality less useful.

Similar to knative/serving#11969, remove sugar-controller as a separate installable YAML, and integrate it into the main eventing controller. Use a namespace-level label selector to enable and disable the sugar controller at the namespace level.

The [current documenta

Has anyone done this safely?

There are currently the following views

• app/views/proposal/new.html.haml with a form to create a new Event
• app/views/proposal/form.html.haml with the edit view
• app/views/proposal/edit.html.haml with 3 lines of html of the edit view
• app/views/proposal/_proposal_form.html.haml with form to edit an Event

This should be cleaned up into new, edit view and a form parti