vbkisk should allow load different than definition.cfg definition file.
Personally I prefer (and use) model where definition.cfg is a symlink to choosen by me VM definition. In symlink model you don't need (and you don't forget) add definition_file_name as argument to post build commands like postinstall/validate/update.
But someone may prefer other workflow, so definition as 3rd argument should be accepted.
vbkisk should allow load different than
definition.cfgdefinition file.Personally I prefer (and use) model where
definition.cfgis a symlink to choosen by me VM definition. In symlink model you don't need (and you don't forget) add definition_file_name as argument to post build commands like postinstall/validate/update.But someone may prefer other workflow, so definition as 3rd argument should be accepted.