The easiest thing would probably be to use the filetype .conf; Ignition will grab anything with that extension. I would have thought storing in data/modules/$yourModuleId would be safe, but you’d probably want to do testing.
Darn, the only annoying thing about that is most of our configs are json out of the ease of use in python/perspective. Any I would miss the syntax highlighting in vs code by switching to .conf
Looks like anything in this folder makes its way through. I just create a random folder at data/modules/not-a-module with a json file and it worked. Not in love with the idea of nesting it in the modules folder, but this will at least work in the short term.
If I go the route of building an extra module so they can live at the data level, do you know of any hooks into the backup utility? Ideally I would like to use data/configs since thats what we have standardized on at this point.
EDIT: A bit cheeky, but if you name the top level folder configs.conf then it looks like whatever wildcard search Ignition is using catches that, however it doesn’t catch a folder named .conf? Maybe something to do with how it tries to avoid .git folders causing issues with project resources.