@matzew @pierDipi @rhuss I was looking at switching to v1beta2 support and kn eventtype create flags. And I was wondering.

There are 2 paths here:

Single --reference flag, that would parse the input for various format:

--reference "broker:<name>"
--reference "broker:<name>:<namespace>"
--reference "channel:<name>:<namespace>"

# fully qualified GVK
--reference "special.eventing.dev/v1beta3:Channel:<name>"
--reference "special.eventing.dev/v1beta3:Channel:<name>:<namespace>"

Multiple flags for well know and popular references (broker, channel, kafka-broker) and single --reference for complete GVK. We already have --broker flag, that I'd like to keep for backward compatibility and convenience of use. Hence the idea with other well known flags.

The issue with this approach we faced in the past is that we will have opinionated defaults, but there's N+ other brokers out there. And we need to fiddle the popularity contest. :)

--broker "<name>"
--channel "<name>"
--broker-kafka "<name>"

# Only accepts qualified GVK
--reference "special.eventing.dev/v1beta3:Channel:<name>"
--reference "special.eventing.dev/v1beta3:Channel:<name>:<namespace>"

CLI: Add support for EventType v1beta2 #1818

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions