-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing a test with datastore fails #2248
Comments
👋 @barreiro |
also, the export json for a test has {
[...]
"datastoreId": 3,
"datastore": {
"type": "COLLECTORAPI"
"id": 3,
[...]
},
} which can result in conflicting information when importing, |
For the records, for this specific use case, there existis a workaround to import a Test and associate it with an existing datastore:
e.g., {
[...]
"datastoreId": 3,
"datastore": null,
[...]
} |
Atm the current behavior of the imports is that if you import something with id's that's already existing, the import will overwrite what's in Horreum. I think we should also improve the documentations regarding imports to highlight this behavior. |
Same for SchemaService.importSchema... |
Perhaps introducing a "duplicate" feature would help. Export/Import should be used as backup/restore, while Duplicate should be used to avoid the tedious process of redefining a lot of properties/settings when creating a new test. |
Yes, or we can add a specific field to TestExport which will dictate what type of import it is (if it's a update or create) |
Describe the bug
The import of a test that uses a datastore other than postgres fails with the following exception on the logs
To Reproduce
Export a test that relies on a custom datastore and re-import it.
Version
0.16.3
The text was updated successfully, but these errors were encountered: