Pillar seeks for a folder with a datastore name, and if it is not found, it terminates silently. The problem is, when migration scripts are placed in some custom directory and the path of this directory is then passed to the Pillar's cli, migration is not executed and no warning or error message is shown either. This seems to be a counterintuitive and obscure behavior.
Please, change it (make Pillar load files from the root of the folder) or explicitly note this behavior in the README and put some warning message in the Registry class for the case of a nonexistent datastore directory.
Pillar seeks for a folder with a datastore name, and if it is not found, it terminates silently. The problem is, when migration scripts are placed in some custom directory and the path of this directory is then passed to the Pillar's cli, migration is not executed and no warning or error message is shown either. This seems to be a counterintuitive and obscure behavior.
Please, change it (make Pillar load files from the root of the folder) or explicitly note this behavior in the README and put some warning message in the Registry class for the case of a nonexistent datastore directory.