[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21776:
---------------------------------------
This pull https://github.com/jbosstools/jbosstools-openshift/pull/984 asks openshift to get the metadata info assuming the full docker tag is resolvable by the openshift cluster. I have tested this with images found on dockerhub but not on my local daemon. As far as I can tell, the code change in the PR works as we would expect. A user has to some way, some how make the image available to the openshift cluster. This means:
* push to the openshift registry
* push to dockerhub
This is the only way you will be able to successfully deploy an image to openshift. As far as I can tell, this is the same behavior you would expect with 'oc new-app --docker-image='
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21716:
-------------------------------------
Once the password is sent to JBT, we still need to add it to Eclipse's Secure storage, which should trigger a prompt for the Master password for Secure Storage. So you'll end with another popup anyway
> Don't re-prompt for password
> ----------------------------
>
> Key: JBIDE-21716
> URL: https://issues.jboss.org/browse/JBIDE-21716
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ]
Pete Muir commented on JBIDE-21716:
-----------------------------------
An environment variable which is set per session (as opposed to written to disk e.g. in to your bash .profile or .bashrc) is pretty secure, as once the session ends the password is removed. This is really not very different from storing the password in a field or variable inside your program.
It's not ideal, and long term we should write a vagrant plugin that can handle this better, but for now...
> Don't re-prompt for password
> ----------------------------
>
> Key: JBIDE-21716
> URL: https://issues.jboss.org/browse/JBIDE-21716
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21794) Can't create new JIRA from AERI webapp
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21794:
-----------------------------------
Summary: Can't create new JIRA from AERI webapp
Key: JBIDE-21794
URL: https://issues.jboss.org/browse/JBIDE-21794
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aeri
Reporter: Fred Bricon
When trying to create a new JIRA from the AERI webapp, after selecting the project, the component and version contain irrelevant values:
http://screencast.com/t/lsQydPTusV
Creating a new ticket then fails
Typing unlisted values in those lists is then ignored, so there really is no way for me to open JIRAs from AERI incidents
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21793:
--------------------------------
Description:
When the installer with the CDK completes, and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
We should try to import the CDK with no-clicks, and hide the detection dialog.
was:We should try to import the CDK with no-clicks, and hide the detection dialog.
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes, and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21793:
--------------------------------
Description:
When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
We should try to import the CDK with no-clicks, and hide the detection dialog.
was:
When the installer with the CDK completes, and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
We should try to import the CDK with no-clicks, and hide the detection dialog.
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21793:
--------------------------------
Affects Version/s: 4.3.1.Beta2
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months