The one solution I was trying so far was to call Vagrant within Vagrant. ( see this commit ]
But this is unwieldy and not an elegant solution. Also Vagrant does not seem to like this approach (it complains saying another vagrant process is already running).
Since all this was being done via the awsinfo plugin I explored trying to call that plugin programmatically - but I guess that needs some ruby magic.
The one solution I was trying so far was to call Vagrant within Vagrant. ( see this commit ]
But this is unwieldy and not an elegant solution. Also Vagrant does not seem to like this approach (it complains saying another vagrant process is already running).
Since all this was being done via the awsinfo plugin I explored trying to call that plugin programmatically - but I guess that needs some ruby magic.