Skip to content
This repository has been archived by the owner on May 6, 2021. It is now read-only.

Use Goa for defining the Idler REST API #91

Open
hferentschik opened this issue Jan 11, 2018 · 4 comments
Open

Use Goa for defining the Idler REST API #91

hferentschik opened this issue Jan 11, 2018 · 4 comments

Comments

@hferentschik
Copy link
Contributor

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
Copy link
Contributor Author

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

@vpavlin
Copy link
Member

vpavlin commented Jan 11, 2018

I completely agree with this

@kishansagathiya
Copy link
Member

@hferentschik is #105 a subset of this issue?

@hferentschik
Copy link
Contributor Author

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.

@hferentschik hferentschik changed the title Use Goa for defining the REST API Use Goa for defining the Idler REST API Feb 27, 2018
@khrm khrm self-assigned this Dec 11, 2018
@hrishin hrishin added this to the M milestone Dec 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants