Skip to main content

CAR service connector framework

Project description

Car Connector Framework

Develop a connector

Use connectors/reference_connector from cp4s-car-connectors project as an example of how this framework is to be used.

A CAR connector project will need to extend the framework classes: BaseFullImport, BaseIncrementalImport, BaseApp, BaseAssetServer and BaseDataHandler, and implement abstract methods of those classes.

Things to note:

  • All communications with CAR digestion microservice are managed by the framework. Connector code normally does not need to access CAR digestion microservice directly

  • The framework is trying to make some intelligent choice for whether to run full vs incremental import. Normally, for performance reasons we would always prefer to run incremental import if one is possible. Some examples of when it is not possible are:

    • The model states for generating delta are not available
    • The model on the CAR side is empty
    • The previous incremental import session failed and a new incremental import session can potentially create a gap in the model data
  • Because of the above the the connector code should properly use (throw/raise) one of three following exceptions when detecting failures:

    • RecoverableFailure is to be used when the failure cannot potentially create a data gap and we can attempt an incremental import session when running next time. One example of a recoverable failure is a connectivity problem.
    • UnrecoverableFailure is to be used when the failure can potentially create a data gap and we must run full import session to recover.
    • DatasourceFailure is to be used when there is datasource API issues.

RecoverableFailure and UnrecoverableFailure are mostly handled in the framework. DatasourceFailure is to be used in the connector code with a corresponding error code. Example: return ErrorCode.TRANSMISSION_AUTH_CREDENTIALS.value. If none of the Failure classes is used, the framework will raise a GENERAL_APPLICATION_FAILURE (Unknown error) and print the error stack.

For more information use guides

Test deploy

https://github.com/IBM/cp4s-car-connectors/blob/develop/deployment/README.md

Publish

Use the guide from PUBLISH.md

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

car-connector-framework-3.0.2rc258.tar.gz (18.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

car_connector_framework-3.0.2rc258-py3-none-any.whl (22.3 kB view details)

Uploaded Python 3

File details

Details for the file car-connector-framework-3.0.2rc258.tar.gz.

File metadata

File hashes

Hashes for car-connector-framework-3.0.2rc258.tar.gz
Algorithm Hash digest
SHA256 5370a8197127dd37d93f91c2b08abe76527908dafee3a21ea355100da2426931
MD5 494f27d8380d1bb883d6378a87697d62
BLAKE2b-256 d465d05da6c8dc52e64630e44d140a57161c5f768e428da7fe567ab6fb740a38

See more details on using hashes here.

File details

Details for the file car_connector_framework-3.0.2rc258-py3-none-any.whl.

File metadata

File hashes

Hashes for car_connector_framework-3.0.2rc258-py3-none-any.whl
Algorithm Hash digest
SHA256 941a9873e0c4c35be3aa7a3b97c637562df08438793092594b337c1cfb81564d
MD5 54daab6ac1e64bab523bef45d129da65
BLAKE2b-256 d76fa8e0e0e574737d622252139c1609d0c5f947dff80c73fda6d1082c83987a

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page