@goanpeca so this is essentially what I want to do with ciocheck (see also the .coveragerc in this PR). The reason ciocheck doesn't work (I think?) is that if I cd into deploy subdir as I do here, ciocheck can't find the .ciocheck in the root dir one level up. (I have .ciocheck-test which does an inherit_from .ciocheck, and I think the inherit_from looks relative to cwd not relative to ciocheck-test?). If I don't cd into the deploy subdir then the module paths are messed up which causes its own trouble.
if you want you can check this branch out and try ./apb test deploy to see what my command here does and play with using ciocheck in kapsel.yml instead..
@havocp could please add any additional context here. The initial version of ciocheck was very limited in terms of where to look for config and stuff. But if you define some "rules" that make sense to you I can make a new release in a week or so.
@havocp could please add any additional context here. The initial version of ciocheck was very limited in terms of where to look for config and stuff. But if you define some "rules" that make sense to you I can make a new release in a week or so.