The next generation of vagrant-adbinfo i.e. vagrant-service-manager [1]
is being designed with below objectives.
*
To provide the user a CLI to configure the ADB/CDK for different use
cases and to provide glue between ADB/CDK and the user's developer
environment.
*
Currently we use a couple of Vagrantfiles and the vagrant-adbinfo
plugin to create these links/configuration changes. However these
methods require the user to change Vagrantfiles based on their needs
and to manually do few things.
* Provide users a tool to control and configure the ADB/CDK from the
developer's workstation without having to `ssh` into the ADB.
The new Vagrant plugin i.e. vagrant-service-manager will have sub
commands and here is the current plan[1] . Let us know if you have some
suggestion.
[1] https://github.com/navidshaikh/vagrant-service-manager/issues/1
Thanks,
Lala
_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools
