Issues with discovery

[duglin]

WIP

https://github.com/cloudevents/spec/blob/master/discovery.md#get-services

• Any Service previously returned to a client that does not appear in this result can be assumed to be no longer available. I think this needs to be limited to just unfiltered queries since a missing entry from a filtered set could mean that it was deleted or that the filtered field changed.
• Discovery endpoints MUST support filtering with the following attributes and MUST reject any unsupported filters. we should probably say what the HTTP response code is.
• is Epoch allowed to be a negative int?
• "name" must be non-empty string
• typo: dataschama

[clemensv]

The CRUD model of the Discovery API needs work.

• On the "services" collection, you can POST a list of services, but no single service. The typical pattern is to add a single item with a 201+Location return code
• On the "services/{id}" node, you can't PUT for an update. POST is not the right choice here.
• On the "services/{id}" node, you need to construct a payload to DELETE. That is clunky and there should be a query parameter option.
• Bulk delete is a potential source of pain

On DELETE, here is a generated code snippet

var existingService = await client.GetServiceAsync(i.ToString());
await client.DeleteServiceAsync(
                    existingService.Id, 
                    new Serviceinstance { Id = existingService.Id, Epoch = existingService.Epoch });

[duglin]

From one of our weekly calls: is a Service supports multiple mechanisms by which it can deliver the events, how will that work? They can list each "protocol" in the "Protocols" array, but there's only one "subscriptionurl" field. Should it be an array too - linked with the protocol?

Also, should "subscriptiondialects" be "subscriptionfilterdialects" instead?

[duglin]

How does kafka work? How does the subscriber get the list of brokers to connect to?

[github-actions]

This issue is stale because it has been open for 30 days with no
activity. Mark as fresh by updating e.g., adding the comment /remove-lifecycle stale.

[duglin]

Moved to: xregistry/spec#8