Navid Shaikh
Navid Shaikh
> @navidshaikh is this still relevant @baude I want to write an atomic scanner which will enlist number of layers for a container image. And information about each layer (`json`...
I can take this.
If given an explicit option for `--cli-version` then machine is not needed to run. This is an advance check, not really needed to have ATM, but IMO we should keep...
> Ideall sccli openshift should print the info in stdout and vsm should pick them and display to user. +1 , this should also help handling services by one single...
> Moreover, we found that vagrant service-manager plugin is not executing extra provisioners present in Vagrantfile (#166) Because proper exit codes were not returned from the opensihft configuration commands from...
and for removing the lines from Vagrantfile https://github.com/projectatomic/adb-atomic-developer-bundle/issues/341
Even if we add feature for auto-generating Vagrantfile, having the openshift information message print part should be moved to vagrant-service-manager from Vagrantfile. As Hardy said, there is no connection.
> If we go this way of printing the message, then we need to remove the shell provisioning lines from provided Vagrantfiles since vagrant up process will print duplicate messages....
> In other directories the user will need to specify the box id as determines by vagrant global-status, eg vagrant service-manager env docker 32869cf. About providing the machine-id, I think...