Create API for connector to run connectors on demand.

[gmej]

New feature available: running connectors on demand via the connector API. @joofio you are going to like this very much.

Check the API definition here: https://gravitate-health.lst.tfo.upm.es/swagger-fosps/?urls.primaryName=FHIR%20Connector#/

List available connectors:

curl --location 'https://gravitate-health.lst.tfo.upm.es/connector/api/connectors/list'

Run a connector:

curl --location --request POST 'https://gravitate-health.lst.tfo.upm.es/connector/api/connectors/fhir-connector-git-ips/run'

Like lenses and preprocessors, FOSPS now automatically discovers future deployments of new connectors.

[gmej]

We can close this as completed, it's already implemented.

[gmej]

I have protected both /connector/api/connectors/list and /api/connectors/CONNECTOR_NAME/run endpoints with authentication, to avoid strange things, as those endpoints execute services in the backend.

[joofio]

how can i test?

[gmej]

New feature available: running connectors on demand via the connector API. @joofio you are going to like this very much.

Check the API definition here: https://gravitate-health.lst.tfo.upm.es/swagger-fosps/?urls.primaryName=FHIR%20Connector#/

List available connectors:

curl --location 'https://gravitate-health.lst.tfo.upm.es/connector/api/connectors/list'

Run a connector:

curl --location --request POST 'https://gravitate-health.lst.tfo.upm.es/connector/api/connectors/fhir-connector-git-ips/run'

Like lenses and preprocessors, FOSPS now automatically discovers future deployments of new connectors.

Look this. We have three connectors availables for now, named:

• "fhir-connector-git-ips" (git repo)
• "fhir-connector-fhir-sync-hl7" (ema ePIs)
• "fhir-connector-git-epi" (git repo) Remember it requieres a valid JWT in the Authorization header.

[joofio]

Tested and seems ok! Great