could you pls tell us a little bit more about your configuration. Why do you think there should be more files than the “import.iini” in /etc/icingaweb2/modules/fileshipper/?
You configured "/opt/import-icinga"as directory where the module should look for files to import. What is the content of this directory? How do you get/create your files to import?
All of them where recognized.
If the path existed I could chose the entry. If it didn’t exist it was mentioned.
If the webserver user did not have access there was a stacktrace when trying to chose a file format.
Only other thing I did was setting permissions for the webserver user and icingaweb2 group on the /etc/icingaweb2/modules/fileshipper directory. But that should already be the case for you, as the config is recognized, but there is some problem with it, it seems.
In case you copy&pasted the imports.ini from somewhere, try creating it manually.
I’ve downgraded to FileShipper version 1.1.0 and now the message of ignoring the folder is gone.
However, now I have the same exact issue as the original post mentions.
There is nothing to choose in the drop-down list. I granted full and open permissions which didn’t help as well.
So, after alooooooot of trials and errors (mainly), I’ve somehow managed to make FileShipper work.
Apparently, version 1.0.0 is working with the configuration I have.
I was able to export hosts from the old server to a json file and import it to the new server using FileShipper.
Now, I have a new issue, and it is how to make a json/csv to include all necessary variables.
Exporting a json/csv for host/service will not contain all parameters (such as warning/critical level for service, or groups for hosts, or contacts info for both)
If it does include the above, it is in an array that I have no idea how to import through FileShipper.
I really hoped that the manuals will have contained something about it.
Sadly, there is not much information out there regarding this module.