Closed kahboom closed 7 years ago
Not implemented in the runtime yet so will have to be moved to the backlog / technical debt.
From IRC:
the expected input parameters will be a connectorId and a map with properties as connectorId sth like "twitter", (not an action btw) and for the props 'consumerKey', 'consumerSecret', 'accessToken' and 'accessTokenSecret' (in the twitter case)
its at ipaas-rest and will look like ... POST to /api/v1/connectors/{id}/verifier with the parameters as json object.
there are two so called 'scopes' which are checked: the first is PARAMETERS which simply validates if all required parameters are there and sound. so no call to a backend. If this fails the check comes back immediately without checking the connectivitiy which is the second scope CONNECTIVITY so, you get always back an array of objects. in the good case, two with both SUCESS.
in the bad case either one element when the initiali validation fails or two, with the validation as SUCESS and the connectivity as ERROR
Example Response: https://gist.github.com/rhuss/b6077883f7fb5937d2e4cd16a971392e#gistcomment-2039927
Example Error Response for Parameter: https://gist.github.com/rhuss/b6077883f7fb5937d2e4cd16a971392e#gistcomment-2039992
Relevant Designs:
Step 1: Define Connection
Step 2: Configure Fields
Step 3: Validate Connection
Step 4: In Progress
Step 5: Error Message
Step 6: Summary
cc @gashcrumb
Overview
Add the ability to validate connections in the UI when creating one. Entails the following:
Relevant Designs
Validation
Validation: In Progress
In cases where it takes more than a second, a progress indicator and message should be presented to the user.
Validation: Failure
Reference