Adding files and directories via modules is sufficient for a few filesystem objects. But if you want to build a big filesystem with a lot of objects, that is very laborious. Additionally, handling filesystem permissions could be a problem with the automatically generated parent folders. Because the processing order of the modules is not fixed, this could lead to issues that behave differently every time you start your mission. You could write scripts to add filesystem objects but not everybody likes that.
So, we think it would be a good idea to allow definition of filesystem objects via mission config. We already parse config for filesystem objects for our default objects. I think we could adapt that mechanism.
Adding files and directories via modules is sufficient for a few filesystem objects. But if you want to build a big filesystem with a lot of objects, that is very laborious. Additionally, handling filesystem permissions could be a problem with the automatically generated parent folders. Because the processing order of the modules is not fixed, this could lead to issues that behave differently every time you start your mission. You could write scripts to add filesystem objects but not everybody likes that.
So, we think it would be a good idea to allow definition of filesystem objects via mission config. We already parse config for filesystem objects for our default objects. I think we could adapt that mechanism.