Currently, all imports that are mapped are written to imports part of import_manifest, when in fact some of them are not actually created.
For example, this Transformation that already exists:
...
Transformations: [
{
id: 1,
name: "MODS to Service Hub profile"
}
],
...
We cannot tell from the import_manifest that lacks the pk_hash if this is new or not, but it can be removed entirely from the imports section if the pk_hash shows the id does not change.
This would allow a "rollback" function, that would delete all model instances in the imports area, without risk of removing something that is in fact not new.
ghukill
commented
5 years ago
Currently, all imports that are mapped are written to
importspart ofimport_manifest, when in fact some of them are not actually created.For example, this Transformation that already exists:
We cannot tell from the
import_manifestthat lacks thepk_hashif this is new or not, but it can be removed entirely from theimportssection if thepk_hashshows the id does not change.This would allow a "rollback" function, that would delete all model instances in the
importsarea, without risk of removing something that is in fact not new.