[jbosstools-issues] [JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env

[Fred Bricon (JIRA)]

Fred Bricon created JBIDE-22575:
-----------------------------------

             Summary: Extract CDK's Docker registry from vagrant service-manager env
                 Key: JBIDE-22575
                 URL: https://issues.jboss.org/browse/JBIDE-22575
             Project: Tools (JBoss Tools)
          Issue Type: Feature Request
          Components: cdk
    Affects Versions: 4.4.0.Final
            Reporter: Fred Bricon


The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441). 
With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK:
{quote}
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://10.1.2.2:2376
export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21

# openshift env:
# You can access the OpenShift console on: https://10.1.2.2:8443/console
# To use OpenShift CLI, run: oc login https://10.1.2.2:8443
export OPENSHIFT_URL=https://10.1.2.2:8443
export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console
export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io

{quote}

We should store the docker registry with a https:// prefix, if the value is not a URL



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)