API client connector

[syndesis-bot]

@rhuss	2017-10-10	Epic, Feature

This epic (scenario) is about a general purpose API Client Connector and the idea of a Connector Builder which can create a connector from a given API description (Swagger) and knows how to deal with OAuth flows in a generic fashion.

@kcbabo please fill in a more complete description of the business case, ideally again in the form of a narrative, including a concrete API which should be tackled first

The details needs to be flashed out in engineering planning meetings. The high-level list was assembled in the F2F Kickoff in Westford and highlights the topics

• Swagger (P0)
• OAS (P1)
• API Connector Builder (P0)
• OAuth Config (P0)
• API Connection Config (P0)
• Action Mapping based on Swagger (P0)
• Data Shape based on Swagger (P0)
• Headers and Query params - how handled (0)
   
  Comments:

• UI - General Settings -> API Connection Builder
• PoC for Swagger + OAuth ingest to
• Swagger-like view of resources for action list

[syndesis-bot]

@sjcox-rh	2017-10-30

Designs for issue found here:

syndesisio/syndesis-ux#49

Please review!
@dongniwang @amysueg @rhuss @gashcrumb @kahboom @kcbabo

[rhuss]

@zregvart Sorry, I forgot again what was missing still and open for Sprint #23. What was it again and could we open issues for this ?

[zregvart]

We agreed to see what we have implemented thus far and see if any functionality is missing. There are 7 issues (currently) linked to this one some of which I placed in Sprint 23. The bigger issue would be to rework the way we handle parameters and separate them from the body in #796 if we deem that the current implementation with the unified parameter/body is too cumbersome.

[zregvart]

I think we're done here. Any outstanding issues should be considered bugs/improvements, i.e. not part of this epic.