vagrant-service-manager 1.0.2 release

[navidshaikh]

• vagrant service-manager env changed behavior - breaks tools #178
• vagrant service-manager env does not show the status of kube #173
• Add command vagrant service-manager box ip #169
• Fix#173: Shows if kubernetes services is running in the box #176
• Evaluate if we need --script-readable for other subcommands #70
• Fix #169: Adds command for displaying box routable IP address #177
• Add status command and separate status from env #179
• Add --script-readable to env and env docker #180
• Fix message for box command on default help #193
• --script-readable vs --machine-readable, eval'able content in output #184
• Fix #135: Refactor command.rb to make commands easier to add/maintain #155
• 'vagrant service-manager restart' not handled correctly #191
• vagrant-service-manager 1.0.2 release #181
• Adds @budhrg as co-maintainer for the plugin #198
• Update README with all commands #187
• Simplify the eval hint for vagrant service-manager env command #200

[navidshaikh]

I'll vote for including the whatever actions needed to fix issue #184 in upcoming release of plugin. And I think that needs to bump the Y stream of the plugin, and the release would be 1.1.0.

@bexelbie : comments ?

[bexelbie]

@navidshaikh I believe the fixes are already in. I'm ambivalent about bumping the Y stream.

[navidshaikh]

Here is the copy of proposal

Command	Extra flag	Output Type
env		eval'able info from docker and openshift
env	--script-readable	k=v format for docker and openshift, with user-readable strings commented
env docker		eval-able (Cannot be changed, except make more easily eval'd on windows? dangerous though)
env docker	--script-readable	K=V properties format with user-readable strings commented
env openshift		eval'able
env openshift	--script-readable	K=V syntax with user-readable strings commented (ie, today's –script-readable format)

And here are the commands and their output. @robstryker @hferentschik @maxandersen please review.

➜ vagrant service-manager env
# docker env:
# Set the following environment variables to enable access to the
# docker daemon running inside of the vagrant virtual machine:
export DOCKER_HOST=tcp://172.28.128.8:2376
export DOCKER_CERT_PATH=/home/nshaikh/work/src/vagrant-service-manager/.vagrant/machines/default/virtualbox/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21
# run following command to configure your shell:
# eval "$(vagrant service-manager env docker)"

# openshift env:
# You can access the OpenShift console on: https://172.28.128.8:8443/console
# To use OpenShift CLI, run: oc login https://172.28.128.8:8443

➜ vagrant service-manager env --script-readable
DOCKER_HOST=tcp://172.28.128.8:2376
DOCKER_CERT_PATH='/home/nshaikh/work/src/vagrant-service-manager/.vagrant/machines/default/virtualbox/docker'
DOCKER_TLS_VERIFY=1
DOCKER_API_VERSION=1.21
OPENSHIFT_URL=https://172.28.128.8:8443
OPENSHIFT_WEB_CONSOLE=https://172.28.128.8:8443/console

➜ vagrant service-manager env docker           
# Set the following environment variables to enable access to the
# docker daemon running inside of the vagrant virtual machine:
export DOCKER_HOST=tcp://172.28.128.8:2376
export DOCKER_CERT_PATH=/home/nshaikh/work/src/vagrant-service-manager/.vagrant/machines/default/virtualbox/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21
# run following command to configure your shell:
# eval "$(vagrant service-manager env docker)"

➜ vagrant service-manager env docker --script-readable
DOCKER_HOST=tcp://172.28.128.8:2376
DOCKER_CERT_PATH='/home/nshaikh/work/src/vagrant-service-manager/.vagrant/machines/default/virtualbox/docker'
DOCKER_TLS_VERIFY=1
DOCKER_API_VERSION=1.21

➜ vagrant service-manager env openshift               
# You can access the OpenShift console on: https://172.28.128.8:8443/console
# To use OpenShift CLI, run: oc login https://172.28.128.8:8443

➜ vagrant service-manager env openshift --script-readable
OPENSHIFT_URL=https://172.28.128.8:8443
OPENSHIFT_WEB_CONSOLE=https://172.28.128.8:8443/console

[maxandersen]

looks good, one comment is that this part from env docker:

# run following command to configure your shell:
# eval "$(vagrant service-manager env docker)"

should not be unique to the docker command.

I would have any output of env just output it at the end (once).
i.e. if I just call env I get this at the end:

# run following command to configure your shell:
# eval "$(vagrant service-manager env)"

if I call env openshift I get:

# run following command to configure your shell:
# eval "$(vagrant service-manager env openshift)"