Add subject to Cloud Event about sources-for-knative HOT 9 CLOSED

Yea, so looking at the ManagedObjectReference, type/value seems reasonable. Though, I wonder if we're processing events from multiple vspheres if we need to prefix it with something else also to avoid collisions?

from sources-for-knative.

Wouldn't source tie the moRef to the concrete vcenter instance, i.e. composite of source and subject is unique?

from sources-for-knative.

Probably, just wanted to jot it down while I was thinking about it :)

from sources-for-knative.

/assign

from sources-for-knative.

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.

from sources-for-knative.

/remove-lifecycle stale

from sources-for-knative.

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.

from sources-for-knative.

related: vmware-samples/vcenter-event-broker-appliance#182 (comment)

from sources-for-knative.

Closing with wontfix since there's currently no easy way to extract a well-defined "subject" from an arbitrary vSphere event.

from sources-for-knative.