Hello
We recently started evaluating DATAGERRY as a new potential CMDB for our company and encountered a major issue. The installation is as standard as it can be for now following the official docs.
We have created a couple of new data types and adding objects the them via the GUI works fine. Also importing CSV files with proper formatting works as expected. But we can’t do the same with JSON which is a priority since we would like to feed DATAGERRY with output from Ansible/facter.
To reproduce the issue I will start from the beginning with creation of the simplest data type:
I add new section and one Text field:
I choose Hostname in META DATA:
No change in ACCESS:
VALIDATION and save:
New Data Type has been created:
To make sure that the JSON output will be proper I will now simply add an Object to this Data Type:
Everything looks good right?
Now let’s export this Object as JSON:
The output file looks like that:
[
{
“public_id”: 230,
“active”: true,
“type”: “LinuxServer”,
“fields”: [
{
“name”: “hostname”,
“value”: “defralinux123”
}
]
}
]
Now, I assume that I should be able to import is back anytime even without any changes made to it:
Selecting LinuxServer as Data Type:
Doesn’t matter if I type 100 or 1000 in Max element field:
After clicking on import DATAGERRY throws an error:
Although it runs with debug option on there is nothing interesting in log files:
[2020-10-30 12:31:02][INFO ] — Parser <class ‘cmdb.importer.parser_object.JsonObjectParser’> was loaded (importer_object_routes.py)
[2020-10-30 12:31:02][DEBUG ] — {‘start_element’: 0, ‘max_elements’: 0, ‘overwrite_public’: True, ‘type_id’: 10} (importer_object_routes.py)
[2020-10-30 12:31:02][INFO ] — Importer <class ‘cmdb.importer.importer_object.JsonObjectImporter’> was loaded (importer_object_routes.py)
It will be exactly the same if I try to export and import JSON with freshly created Data Type. The same procedure with CSV works perfectly fine with both Data Types and Objects.
We really like DATAGERRY, how simple it is and how smooth it works but without a proper JSON import we can’t continue any further testing.
Thank you.