kn source list-types - List all available source types

[navidshaikh]

This command list the source type CRDs, as discussed in the MVP doc.

It's all about to list all possible source types which can be used with a "kn source create"

General description from the eventing spec documentation (might become outdated, the spec is the authorative specification):

# List all available builtin, plugin and generic sources which can be 
# used with the connected cluster
$ kn source list-types

TYPE              NAME                                         DESCRIPTION
kafka             kafkasources.sources.eventing.knative.dev    Kafka messages
apiserver         apiserversources.sources.eventing.knative.de Import Kubernetes event
cronjob           cronjobsources.sources.eventing.knative.dev  Periodic event from cron
twitter           twitter.mycompany.com                        Import tweets          
storage           storages.events.cloud.run
pullsubscriptions pullsubscriptions.pubsub.cloud.run

In this example output, typed and generic sources are listed together. For generic sources a short type name calculated from the full CRD name as described in Guessable CRD names is shown. Optionally an additional column should be presented in verbose output to indicate the kind of source support (builtin/plugin/generic).
This is just a sample output, the details would have to be determined during implementation. For generic sources it should be checked whether a description could be extracted from the CRD directly so that it could be presented in the Description column.
The list above is created by performing the following steps:

• A set of all CRDs with a label indicating that this CRD is a Knative Eventing Source is obtained from the cluster.
• For all built in-types like cronjob, apiserver and container it is checked whether their associated CRD names are in this initial set. If so, the names removed are from the set, and the found type is printed out with a fixed description.
• All kn plugins that start with a name kn-source- are called with “kn-source- manifest” ( could be e.g. “twitter” like in the example above). This command is supposed to return metadata as a JSON structure including the description and the supported full CRD name. It is checked if this CRD name is in the set of CRDs obtained from the cluster, and if so, it is printed out and the CRD name removed from that CRD set.
• For all CRDs remaining in this CRD set, the CRD name is printed out with a short name for the CRD. Before printing out that name it could be checked whether the CRD is really suitable to be used as generic Source by verifying that it conforms to the Eventing Source specification.

[navidshaikh]

Separated the list-type in this issue from #497

[navidshaikh]

/assign

[rhuss]

@navidshaikh Is this task done or is there still something needed ? (like plugin support)

[navidshaikh]

@rhuss : Plugin support remaining, also there was a mention about listing whether the source type is builtin or otherwise. So we can add a check list or fork new issues.

[rhuss]

I would create a new issue, so that I can move that to the "Done" column in https://github.com/knative/client/projects/1 ;-)

[navidshaikh]

Created #633 for remaining items.

/close

[knative-prow-robot]

@navidshaikh: Closing this issue.

In response to this:

Created #633 for remaining items.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.