Implement Odoo to PostgreSQL sync service - #10
Open
esmaeil-taheri wants to merge 25 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backend service that syncs Contacts, Products, Sale Orders and Sale Order Lines
from Odoo (XML-RPC) into PostgreSQL. Idempotent and re-runnable (upsert by odoo_id,
no duplicates), with per-record error isolation and a full audit trail in
sync_runs / sync_logs. Built with clean architecture + dependency injection.
How to run
Brings up Odoo + its DB, seeds Odoo test data, runs migrations, then the sync.
Local run:
cp .env.example .env pip install -e . alembic upgrade head python -m app.mainDetails in
docs/USER.md.How to run tests
21 tests (entities, mappers, repositories, sync use case), ~77% coverage.
Key architecture decisions
(domain ← application ← infrastructure).
OdooClient;swapping the ERP touches one adapter, not the business logic.
IDBConnectionport — swapping PostgreSQL for anotherDB touches one adapter.
odoo_idas primary key for synced tables → foreign keys align without idtranslation.
odoo_id, then update (exists) or save (new).failure is logged + counted and the batch continues (no full rollback).
More in
docs/TECHNICAL.md.