search

fabric8-services / fabric8-jenkins-idler

OpenShift.io service to idle resp.unidle Jenkins instances
Apache License 2.0
4 stars 15 forks source link

Use Goa for defining the Idler REST API #91

Open hferentschik opened 6 years ago

hferentschik commented 6 years ago

Currently, the REST API is defined and served by httprouter. We should switch to Goa to design and serve the API. Partly because it aligns with the other services and partly since this allows for automatic client generation on the caller side of the Idler (aka Proxy).

hferentschik commented 6 years ago

@vpavlin FYI, I think switching to Goa is probably the best approach in terms of achieving the discussed decoupling of Idler and Proxy.

vpavlin commented 6 years ago

I completely agree with this

kishansagathiya commented 6 years ago

@hferentschik is https://github.com/fabric8-services/fabric8-jenkins-idler/issues/105 a subset of this issue?

hferentschik commented 6 years ago

is #105 a subset of this issue?

No, there are several things here. One issue (this one) is about using Goa to define the REST API for the Idler itself. It's own API. #105 is about using Goa's ability to generate a client from a given Goa spec file. I would consider this issue to be the more important one.