Mechanism to migrate organisation metadata

avniproject / integration-service

Service for integration Avni with other systems

GNU Affero General Public License v3.0

0 stars 2 forks source link

Mechanism to migrate organisation metadata #73

Closed vinayvenu closed 1 year ago

vinayvenu commented 1 year ago

Story

As an implementer, I would like to have a mechanism to migrate metadata from one organisation to another so that

moves from test to production is error-free
modifications of metadata can be done easily

Solution notes

GET apis for metadata zip
POST apis for metadata zip
This need not be a batch process. Can happen online
Add and use uuids everywhere
Add voiding of metadata and use it in code
Zip upload should be idempotent
Regular auth

1t5j0y commented 1 year ago

Avni Integration.postman_collection.zip

ashusvnath commented 1 year ago

Able to download metadata zip after login using /int/export
Able to re-upload the downloaded zip without any errors (idempotent) to /int/import

ashusvnath commented 1 year ago

issue discovered: When a metadata zip is downloaded as parts of integration_system1 (say goonj) and uploaded to another org integration_system2 (say goonj-test), the DB metadata for goonj move to goonj-test and no configs for goonj can be found in the DB.

@1t5j0y FYINA

1t5j0y commented 1 year ago

Root cause of bug: During import, existing records were fetched only by uuid instead of by uuid and integration system (of importing user). Added fix to search by uuid and integration system.