[jbosstools-issues] [JBoss JIRA] (JBIDE-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

[Jeff Cantrill (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201641#comment-13201641 ] 

Jeff Cantrill commented on JBIDE-22177:
---------------------------------------

Notes from my conversation with bparees regarding what 'oc new-app NAME' generally does.

Note: openshift project matches docker username in a pullspec.  User must have perms to this project
in order to use image.

‘New-app’ roughly does the following given its arg:

* Arg matches existing IS
** Ref existing IS
* Arg matches image in public registry
** Create imagestream ref to arg
* Arg matches only Image locally
** IS pointed to ref of image in project and need to push image to registry

which means for JBT, since we are starting (potentially) with a local image and that image may or may not be pulled from a public registry should:

# Check docker pull spec against project imagestreams and 'openshift' imagestreams and use that if there is a match
# Create an IS to the pull spec with the 'username' modified to equal project name. inform user they need to push the image (until we can tag and push) and how.

> Docker Image host is missing from Deployment Config when deploying from a private registry
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22177
>                 URL: https://issues.jboss.org/browse/JBIDE-22177
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, upstream
>    Affects Versions: 4.3.1.CR1
>            Reporter: Fred Bricon
>            Assignee: Jeff Cantrill
>             Fix For: 4.4.0.Alpha2
>
>
> If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy



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