[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19008:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> As a user, I want to delete OpenShift resources
> -----------------------------------------------
>
> Key: JBIDE-19008
> URL: https://issues.jboss.org/browse/JBIDE-19008
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> We should allow users to remove OpenShift v3 resources.
> Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19008:
------------------------------------------
postponing to 4.3.0.Beta1, nothing that we have to finish for Alpha2
> As a user, I want to delete OpenShift resources
> -----------------------------------------------
>
> Key: JBIDE-19008
> URL: https://issues.jboss.org/browse/JBIDE-19008
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> We should allow users to remove OpenShift v3 resources.
> Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19108:
------------------------------------------
As far as I understand this is not an issue in OpenShift but rather something that should get fixed in server. Removing openshift component.
> Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19108
> URL: https://issues.jboss.org/browse/JBIDE-19108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
> Attachments: JBIDE-19108_1.png, JBIDE-19108_2.png, JBIDE-19108_3.png, server_already_running.png
>
>
> If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection.
> !server_already_running.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19108:
-------------------------------------
Component/s: (was: openshift)
> Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19108
> URL: https://issues.jboss.org/browse/JBIDE-19108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
> Attachments: JBIDE-19108_1.png, JBIDE-19108_2.png, JBIDE-19108_3.png, server_already_running.png
>
>
> If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection.
> !server_already_running.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19371) Allow OpenShiftRedirectionStrategy to determine the auth scheme
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19371:
------------------------------------------
postponing to Beta1, nothin we'd have to finish for Alpha2
> Allow OpenShiftRedirectionStrategy to determine the auth scheme
> ---------------------------------------------------------------
>
> Key: JBIDE-19371
> URL: https://issues.jboss.org/browse/JBIDE-19371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> Introducing an authorization client which is able to determine how to authenticate when it gets a 401 and includes the following headers:
> (org.apache.http.Header[]) [Www-Authenticate: Basic realm="openshift", Date: Wed, 25 Feb 2015 20:11:49 GMT, Content-Length: 0, Content-Type: text/plain; charset=utf-8]
> Add method to identify the auth scheme and return the realm. Update the 'canconnect' endpoint to use this function.
> This was achieved by trying to auth with empty username and password
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month