[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22747:
-----------------------------------------------
[~adietish], I thought this is fixed with JBIDE-22709, did I missed something and some items still do not work?
> Several context menu items in context menu of an OpenShift 2 server adapter do not work
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22747
> URL: https://issues.jboss.org/browse/JBIDE-22747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v2
> Fix For: 4.4.1.AM3
>
>
> When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view.
> Following context menu items are not working:
> - OpenShift - Port Forwarding...
> - OpenShift - Tail Files...
> - OpenShift - Snapshot - Save...
> - OpenShift - Snapshot - Restore/Deploy...
> - OpenShift - Details...
> - OpenShift - Edit Embedded Cartridges...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-22747 at 7/26/16 8:49 PM:
------------------------------------------------------------------------
[~adietish], I thought this is fixed with JBIDE-22709, did I miss something and some items still do not work?
was (Author: scabanovich):
[~adietish], I thought this is fixed with JBIDE-22709, did I missed something and some items still do not work?
> Several context menu items in context menu of an OpenShift 2 server adapter do not work
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22747
> URL: https://issues.jboss.org/browse/JBIDE-22747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v2
> Fix For: 4.4.1.AM3
>
>
> When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view.
> Following context menu items are not working:
> - OpenShift - Port Forwarding...
> - OpenShift - Tail Files...
> - OpenShift - Snapshot - Save...
> - OpenShift - Snapshot - Restore/Deploy...
> - OpenShift - Details...
> - OpenShift - Edit Embedded Cartridges...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22695 at 7/26/16 6:35 PM:
-------------------------------------------------------------------
[~mlabuda] can you please explain "Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero"?
I agree that we shouldnt do much magic IMHO according to the principle "if you cant do it fully awesome and magical, dont do it but provide tools to achieve this manually".
Maybe we're missing missing some ability to backup and restore?
This could be achieved quite easily by offering the ability to dump resources to local files? We already have the ability to create resources from files via New > resource in the context menu.
Maybe offering the user the ability to duplicate existing resources would fullfill this equally well, allowing the user to create some backup of a state at time X?
[~jeffmaury] [~fbricon] Thoughts?
was (Author: adietish):
[~mlabuda] can you please explain "Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero"?
I agree that we shouldnt do much magic IMHO according to the principle "if you cant do it fully awesome and magical, dont do it but provide tools to achieve this manually".
Maybe we're missing missing some ability to backup and restore?
This could be achieved quite easily by offering the ability to dump resources to local files? We already have the ability to create resources from files via New > resource in the context menu.
Maybe offering the user the ability to duplicate existing resources would fullfill this equally well, allowing the user to create some backup of a state at time X?
[~jeffmaury][~fbricon] Thoughts?
> Environment Variables of application deployment should have different workflow
> ------------------------------------------------------------------------------
>
> Key: JBIDE-22695
> URL: https://issues.jboss.org/browse/JBIDE-22695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue:
> Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest).
> There are 2 options:
> a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller).
> b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22695:
------------------------------------------
[~mlabuda] can you please explain "Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero"?
I agree that we shouldnt do much magic IMHO according to the principle "if you cant do it fully awesome and magical, dont do it but provide tools to achieve this manually".
Maybe we're missing missing some ability to backup and restore?
This could be achieved quite easily by offering the ability to dump resources to local files? We already have the ability to create resources from files via New > resource in the context menu.
Maybe offering the user the ability to duplicate existing resources would fullfill this equally well, allowing the user to create some backup of a state at time X?
[~jeffmaury][~fbricon] Thoughts?
> Environment Variables of application deployment should have different workflow
> ------------------------------------------------------------------------------
>
> Key: JBIDE-22695
> URL: https://issues.jboss.org/browse/JBIDE-22695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue:
> Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest).
> There are 2 options:
> a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller).
> b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22694:
-------------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM3)
> Environment Var Wizard: Improve deletion of environment variables
> -----------------------------------------------------------------
>
> Key: JBIDE-22694
> URL: https://issues.jboss.org/browse/JBIDE-22694
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22694 at 7/26/16 6:20 PM:
-------------------------------------------------------------------
temptatively set 4.4.1.Final as fixVersion. [~fbricon] how many versions do we have until 4.4.1 goes final?
was (Author: adietish):
temptatively set 4.4.1.AM3 as fixVersion (even though this is not urgent). [~fbricon] how many versions do we have until 4.4.1 goes final?
> Environment Var Wizard: Improve deletion of environment variables
> -----------------------------------------------------------------
>
> Key: JBIDE-22694
> URL: https://issues.jboss.org/browse/JBIDE-22694
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22747:
------------------------------------------
[~jeffmaury][~fbricon] this is urgent and should get fixed in this sprint i believe. Agree?
> Several context menu items in context menu of an OpenShift 2 server adapter do not work
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22747
> URL: https://issues.jboss.org/browse/JBIDE-22747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v2
> Fix For: 4.4.1.AM3
>
>
> When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view.
> Following context menu items are not working:
> - OpenShift - Port Forwarding...
> - OpenShift - Tail Files...
> - OpenShift - Snapshot - Save...
> - OpenShift - Snapshot - Restore/Deploy...
> - OpenShift - Details...
> - OpenShift - Edit Embedded Cartridges...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22747:
----------------------------------------
Assignee: Andre Dietisheim
> Several context menu items in context menu of an OpenShift 2 server adapter do not work
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22747
> URL: https://issues.jboss.org/browse/JBIDE-22747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v2
> Fix For: 4.4.1.AM3
>
>
> When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view.
> Following context menu items are not working:
> - OpenShift - Port Forwarding...
> - OpenShift - Tail Files...
> - OpenShift - Snapshot - Save...
> - OpenShift - Snapshot - Restore/Deploy...
> - OpenShift - Details...
> - OpenShift - Edit Embedded Cartridges...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22694:
------------------------------------------
temptatively set 4.4.1.AM3 as fixVersion (even though this is not urgent). [~fbricon] how many versions do we have until 4.4.1 goes final?
> Environment Var Wizard: Improve deletion of environment variables
> -----------------------------------------------------------------
>
> Key: JBIDE-22694
> URL: https://issues.jboss.org/browse/JBIDE-22694
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.1.AM3
>
>
> Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months