Allow multiple exec scripts

[Eric Hammond]

It would be nice to allow the user to specify multiple --exec scripts (by command line or configuration option) and have them run in the order they were specified.

This would allow users to plug in multiple different setup scripts from different sources, each designed to do a particular task, without having to create their own wrapper script calling each of them.

This is especially true for "vmbuilder --ec2". Currently to build a viable EC2 image there is a default exec script which is required to be run to set up the image appropriately for the EC2 environment. Once this is released, other users will want to customize their own EC2 images with their own scripts as well. Having a single exec script forces them to either modify the default script (creating maintenance headaches in the future) or create an extra wrapper script knowing where the default script is.

[Nick Barcet (nijaba)]

Even though this could be usefull in some cases, I think --exec script
should be left for users to use and not for us to provide additional
functionalities. vmbuilder's plugin mechanism offers an excellent way
of extending functionalities without using the --exec command and I
would expect ec2 building to use this mechanism instead of relying on
--exec.

  status confirmed
  priority whishlist

[Nick Barcet (nijaba)]

Even though this could be usefull in some cases, I think --exec script
should be left for users to use and not for us to provide additional
functionalities. vmbuilder's plugin mechanism offers an excellent way
of extending functionalities without using the --exec command and I
would expect ec2 building to use this mechanism instead of relying on
--exec.

  status confirmed
  importance whishlist

[Eric Hammond (esh)]

Sounds fine to me for the EC2 plugin to use a different mechanism to build the default base install. I still think it would be nice (wishlist) to let users specify multiple exec scripts.