-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Importing and updating a component config between two deployments does not work for the following reasons:
- the IC ID of the original instance gets stored in the export file
- the export file can be uploaded/imported in a different deployment without error although the IC ID doesn't exist
- updating the imported config, the original IC isn't found ("Record not Found in DB: type record not found") - this can happen easily when the original deployment has more ICs than the newer one
Resulting TODOs:
- on import, the IC ID should get checked. Either
- return an error
- store the component config without IC ID
- make the issue known/manageable to the user in the frontend
- make the update method check only the new IC ID? (does it matter for some reason that the old one isn't found at this point?)
- consider whether it makes sense to not export the IC ID
- create frontend issue(s) accordingly
Metadata
Metadata
Assignees
Labels
No labels