5sControl / 5sControl/odoo_apps
Import Users data from Manifest to Odoo
- 主要语言
- HTML
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
描述
**Main entities:**
- Odoo module
- API on Digital Ocean
- Manifest
**Task:**
Organize the import of users from Manifest to Odoo via API.
**Data Flow:**
Manifest → API (Digital Ocean) → Odoo
**UserImportService**
- _UserManifestClient_ - to work with the Manifest API.
- _UserMapper_ - to convert data from Manifest to Odoo format.
- _UserOdooService_ - for sending data to Odoo.
**AuthService**
- _Manifest (JWT) Auth_ - API is authorized to Manifest via JWT
- _Auth (token)_ - Odoo API authorization (The API is closed and protected - it does not give data to anyone.
In order for Odoo to send an API request, it must prove that it is a trusted client. For this purpose, Odoo stores the API Token (Bearer Token))
**Odoo API Manifest Interface**
1. **Odoo sends request to API -> get users**
Odoo runs a CRON job (every **N** minutes or manually). CRON-a task - send request to API (**FOR NOW USED A MANUAL METHOD!**)
2. **API is authorized to Manifest via JWT**
3. **API retrieves user data from Manifest**
4. **API mapped data**
5. **API sends data back to Odoo**
6. **In Odoo, data is written to the model**
贡献指南
这个仓库没有索引到贡献指南
调研方向
The issue describes a data pipeline from Manifest to Odoo. Start by examining the existing Odoo module structure and locating any CRON job setup. Look for API client code for Manifest (JWT auth) and Odoo (token auth). The UserImportService with its three components (UserManifestClient, UserMapper, UserOdooService) needs to be implemented. Check for existing model definitions in Odoo to understand the target data format. 'Done' means users are successfully imported via the API on a schedule.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- api, backend, data-engineering
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100