[JBoss JIRA] (JBIDE-21355) Edit resource properties from Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21355?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21355:
-------------------------------------
Labels: new_and_noteworthy openshift_v3 (was: new_and_noteworthy)
> Edit resource properties from Properties view
> ---------------------------------------------
>
> Key: JBIDE-21355
> URL: https://issues.jboss.org/browse/JBIDE-21355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Labels: new_and_noteworthy, openshift_v3
> Fix For: 4.4.x
>
>
> Resources are currently editable from a source editor (see JBIDE-20761). It'd be nice to have a more fined grained approach, and have the properties be directly editable from the Properties view (eg. modify label, change git source url)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21668) Fix collection setters in ResourcesUIModel
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21668?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21668:
-------------------------------------
[~scabanovich] please sync' up with [~tmader] before starting anything
> Fix collection setters in ResourcesUIModel
> ------------------------------------------
>
> Key: JBIDE-21668
> URL: https://issues.jboss.org/browse/JBIDE-21668
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> Created as follow up to JBIDE-21590.
> Collections setters in ResourcesUIModel, for instance
> {code}
> public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) {
> firePropertyChange(PROP_BUILD_CONFIGS, resources.get(ResourceKind.BUILD_CONFIG), resources.put(ResourceKind.BUILD_CONFIG, new ArrayList<>(buildConfigs)));
> }
> {code}
> fire incorrect newValue object, because java.util.Map.put(key, value) returns old object associated with the key, not the one just set.
> At this moment, this does not create any bugs, because these setters are still not used, all changes go through ResourcesUIModel.add, ResourcesUIModel.remove, ResourcesUIModel.update that have correct notification. But bugs may appear as soon as collection setters are used, so that they better be fixed, for instance this way :
> {code}
> public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) {
> setResourcesForKind(buildConfigs, ResourceKind.BUILD_CONFIG);
> }
> private void setResourcesForKind(Collection<IResourceUIModel> list, String kind) {
> List<IResourceUIModel> oldList = resources.get(kind);
> List<IResourceUIModel> newList = new ArrayList<IResourceUIModel>(list);
> resources.put(kind, newList);
> firePropertyChange(getProperty(kind), oldList, newList);
> }
> {code}
> and with use of private setResourcesForKind all other setters will remain one-liners.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-18428) Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18428?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-18428.
--------------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.x)
Resolution: Won't Fix
> Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18428
> URL: https://issues.jboss.org/browse/JBIDE-18428
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v2, upstream
> Fix For: 4.4.0.Alpha3
>
> Attachments: unknown-error.png
>
>
> The issues is that OpenShift Online responds with *500 Internal Server Error* when invalid credentials are being used (where *401 Unauthorized* is expect)
> {code}
> curl -v --user adietish@redhat.com:bogus https://openshift.redhat.com/broker/rest/user* Adding handle: conn: 0xaa8a80
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0xaa8a80) send_pipe: 1, recv_pipe: 0
> * About to connect() to openshift.redhat.com port 443 (#0)
> * Trying 50.19.249.93...
> * Connected to openshift.redhat.com (50.19.249.93) port 443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
> * Server certificate:
> * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
> * start date: Jul 23 00:00:00 2014 GMT
> * expire date: Jul 27 12:00:00 2017 GMT
> * common name: openshift.redhat.com
> * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > GET /broker/rest/user HTTP/1.1
> > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> > User-Agent: curl/7.32.0
> > Host: openshift.redhat.com
> > Accept: */*
> >
> < HTTP/1.1 500
> < Cache-Control: no-cache, private
> < Content-Type: application/json; charset=utf-8
> < Date: Wed, 24 Sep 2014 10:18:21 GMT
> < ProxyTime: D=374659
> * Server Apache/2.2.15 (Red Hat) is not blacklisted
> < Server: Apache/2.2.15 (Red Hat)
> < Status: 500
> < Strict-Transport-Security: max-age=15768000, includeSubDomains
> < Vary: Accept-Encoding,User-Agent
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
> < X-Rack-Cache: miss
> < X-Request-Id: b25500e832d6bbebb1bc7eee5e3175b4
> < X-Runtime: 0.367919
> < X-UA-Compatible: IE=Edge,chrome=1
> < Content-Length: 376
> < Connection: keep-alive
> <
> * Connection #0 to host openshift.redhat.com left intact
> {"api_version":1.7,"data":null,"messages":[{"exit_code":1,"field":null,"index":null,"severity":"error","text":"Unable to authenticate the user. Please try again and contact support if the issue persists. \nReference ID: b25500e832d6bbebb1bc7eee5e3175b4"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7],"type":null,"version":"1.7"}
> {code}
> stg.openshift.redaht.com is responding with the correct 401:
> {code}
> [adietish@localhost openshift-java-client]$ curl -v --proxy https://file.rdu.redhat.com:3128 --user adietish@redhat.com:bogus https://stg.openshift.redhat.com/broker/rest/user
> * Adding handle: conn: 0x178dae0
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x178dae0) send_pipe: 1, recv_pipe: 0
> * About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
> * Trying 10.11.5.7...
> * Connected to file.rdu.redhat.com (10.11.5.7) port 3128 (#0)
> * Establish HTTP proxy tunnel to stg.openshift.redhat.com:443
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > CONNECT stg.openshift.redhat.com:443 HTTP/1.1
> > Host: stg.openshift.redhat.com:443
> > User-Agent: curl/7.32.0
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.0 200 Connection established
> <
> * Proxy replied OK to CONNECT request
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> * Server certificate:
> * subject: CN=stg.openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
> * start date: Apr 30 00:00:00 2014 GMT
> * expire date: May 04 12:00:00 2016 GMT
> * common name: stg.openshift.redhat.com
> * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > GET /broker/rest/user HTTP/1.1
> > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> > User-Agent: curl/7.32.0
> > Host: stg.openshift.redhat.com
> > Accept: */*
> >
> < HTTP/1.1 401
> < Date: Wed, 24 Sep 2014 10:19:22 GMT
> * Server Apache/2.2.15 (Red Hat) is not blacklisted
> < Server: Apache/2.2.15 (Red Hat)
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
> * Authentication problem. Ignoring this.
> < WWW-Authenticate: Basic realm="Application"
> < X-UA-Compatible: IE=Edge,chrome=1
> < Cache-Control: no-cache, private
> < X-Request-Id: 5217138e18f0e036b1880d006e4c3cb6
> < X-Runtime: 0.569233
> < X-Rack-Cache: miss
> < Status: 401
> < Content-Length: 27
> < Content-Type: text/html; charset=utf-8
> < Vary: Accept-Encoding,User-Agent
> < Strict-Transport-Security: max-age=15768000, includeSubDomains
> < ProxyTime: D=574882
> <
> HTTP Basic: Access denied.
> * Connection #0 to host file.rdu.redhat.com left intact
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21634:
--------------------------------
Labels: explorer new_and_noteworthy openshift_v3 properties (was: explorer openshift_v3 properties)
> Explorer, Properties: Allow a user to scale their deployment
> ------------------------------------------------------------
>
> Key: JBIDE-21634
> URL: https://issues.jboss.org/browse/JBIDE-21634
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, new_and_noteworthy, openshift_v3, properties
> Fix For: 4.4.0.Alpha1
>
>
> The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
> 1. deployment (replication controller)
> 2. eclipse view of a deployment (service) -> walk back to the currrent deployment
> 3. pod -> walk back to the current deployment
> updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21634 at 5/24/16 3:45 PM:
--------------------------------------------------------------
adding new_and_noteworthy label
was (Author: fbricon):
adding new-and-noteworthy label
> Explorer, Properties: Allow a user to scale their deployment
> ------------------------------------------------------------
>
> Key: JBIDE-21634
> URL: https://issues.jboss.org/browse/JBIDE-21634
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, new_and_noteworthy, openshift_v3, properties
> Fix For: 4.4.0.Alpha1
>
>
> The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
> 1. deployment (replication controller)
> 2. eclipse view of a deployment (service) -> walk back to the currrent deployment
> 3. pod -> walk back to the current deployment
> updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-21634.
-------------------------------
Resolution: Done
> Explorer, Properties: Allow a user to scale their deployment
> ------------------------------------------------------------
>
> Key: JBIDE-21634
> URL: https://issues.jboss.org/browse/JBIDE-21634
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, new_and_noteworthy, openshift_v3, properties
> Fix For: 4.4.0.Alpha1
>
>
> The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
> 1. deployment (replication controller)
> 2. eclipse view of a deployment (service) -> walk back to the currrent deployment
> 3. pod -> walk back to the current deployment
> updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months