footprint-proto defines messages to deliver from client-SDK to footprint-ingestor server, you would like to ship to our system (an example can be seen here).
Flow *
-
Once the MR is merged, we would publish the generated code to the
footprint-dtorepository from which you can import the relevang golang packages. This stage, you can download new version for client to send message but processor no handle new change on proto file -
After releasing version on footprint, pipeline continues release
footprint-processorversion. In this stage, your backend processor can update new ProcessorSDK version, then processor can handle this.
Schema Backward Compatible *
Pipeline has stages (partially, fully) to check compatible
You needs keeping version (BACKWARD COMPATIBLE), only changes allowed with lastest schemas:
- Delete fields (options or required)
- Add optional fields
With othercases, Schema must to increase new version
-
Add required fields
-
Add more validator
…
More details avro schemas registry
Installation
Java
Swift
Golang
Python
JavaScript
[Click here]