API registry supposed to be working ?

[rhuss]

Before opening issues I wonder whether the ApiRegistry microservice is supposed to be working ? I ask because I get strange protocol errors which indicate that there has not been update recently here.

[davsclaus]

No I think its going to the sandbox, as apiman project itself is likely the place for api registry and governancen and all that for this.

@rajdavies @jstrachan is that correct I did I misunderstand something?

[KurtStam]

Correct Apiman now has a service catalog page to browse all services, at
/apimanui/api-manager/catalog/api-catalog which looks like:
https://www.dropbox.com/s/ntcsg4ksb70jk0a/Screenshot%202016-01-13%2015.32.13.png?dl=0

[davsclaus]

Thanks @KurtStam - I think we should remove the old ApiRegistry then, @jstrachan any thoughts?

[KurtStam]

@jstrachan @rhuss I was thinking to make a pass over all the quickstarts now to add the official k8s Service Annotations (https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/service-discovery.md) for the WADL documents. That way all api documents should get reported in the Apiman Catalog, and it would fully replace the api-registry functionality. I can remove it after that, sound ok?

[davsclaus]

+1 from me

[rajdavies]

+1 from me too

[KurtStam]

Removing the api-registry and tracking the addition of the service annotations in the ipaas-quickstart project (fabric8io/ipaas-quickstarts#1175)