[jbosstools-issues] [JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-22239:
---------------------------------------

Based on the original impl of how we support scaling I would expect:

* scale deployment config - updates DC and RC
* scale deployment/replication controller - updates only the rc

This would imply further changes to the DC will over-write any changes to the RC.  But, this PR/issue may no longer be valid since the rework I added for #JBIDE-23030 which changes our scaling workflow to utilize the 'scale' endpoint over direct edit of a DC.

> Allow a user to choose to permanently update their desired replicas for their deployment 
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22239
>                 URL: https://issues.jboss.org/browse/JBIDE-22239
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Jeff Cantrill
>            Assignee: Viacheslav Kabanovich
>              Labels: openshift_v3
>             Fix For: 4.4.1.Final
>
>
> When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting.  Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their.  Suggest:
> * Adding a custom dialog in the "..to.." option
> * Update to use a spinner
> * Add a checkbox to 'make the change perminent'
> * If checkbox=true, you should only need to update the dc if it has a configchange trigger.
> * Optionally show checkbox if unable to determine the dc associated with the deployment.



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