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

Metadata

Release files for car-connector-framework 3.0.1rc259

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for car-connector-framework 3.0.1rc259
File	Size	Uploaded
car-connector-framework-3.0.1rc259.tar.gz	18.1 kB	Apr 11, 2023	Details

Built distribution (wheel)

Table of built distributions (wheels) for car-connector-framework 3.0.1rc259
File	Interpreter	ABI	Platform	Reset
car_connector_framework-3.0.1rc259-py3-none-any.whl 22.4 kB Apr 11, 2023	Python 3	none	any	Details

Total release size: 40.5 kB

Release files / car-connector-framework-3.0.1rc259.tar.gz

Download URL	car-connector-framework-3.0.1rc259.tar.gz
Size	18.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`741932a077d2c59774ff41beb6b8222f00cbb08c13068fd23d374058167aacb9`
BLAKE2b-256 checksum How to use checksums	`b9d2b098ef41e100420c92402bbc19076389e7c1678c0958e61a71ef7f140598`
Upload date	Apr 11, 2023
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/4.0.2 CPython/3.9.6`

Release files / car_connector_framework-3.0.1rc259-py3-none-any.whl

Download URL	car_connector_framework-3.0.1rc259-py3-none-any.whl
Size	22.4 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`7d0f25c8e5999ac53d5ae931c9cdc8975959121be39cbc8b5ae067c1374f79f4`
BLAKE2b-256 checksum How to use checksums	`080be99a69749768fbf51c7131b3c49dee2615ca0146f67c0533e923eb909cae`
Upload date	Apr 11, 2023
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/4.0.2 CPython/3.9.6`