Description

In 3.x, users had an easy way to roll back from a Deployment Config. This is a feature gap in 4.0 and is an huge usability issue for customers coming from 3.x to 4.x. Since we are defaulting users to use Deployments rather than Deployment Configs, we should support Rollback for both Deployments and Deployment Configs

Acceptance Criteria

To enable Rollbacks for Deployment Configs, we will be enabling a Rollback action off of valid Replication Controllers:

• As a user, I should be able to Rollback *inactive* Replication Controllers associated with an *active* Deployment Config
  • The Rollback action for active Replication Controllers associated with an active Deployment Config will be disabled
• As a user, when clicking on the Rollback action of a Replication Controller, I should have 3 options, which are unselected by default:
  • replica count and selector
  • deployment strategy
  • deployment trigger

To enable Rollbacks for Deployments, we will be enabling a Rollback action off of valid Replication Sets:

• As a user, I should be able to Rollback *inactive* Replica Sets
• As a user, when clicking on the Rollback action of a Replica Set, the user needs to confirm the rollback action.

Notes

• The modal title should be Rollback
• The intro text for the Replication Controller modal should be Use the following settings from replica name when rolling back:
• The modal should have Rollback and Cancel buttons

This matches the capabilities in OpenShift 3.x

FLOW in 3.X

Thoughts for 4.X

This is the 3.x code for deployment config: https://github.com/openshift/origin-web-console/blob/enterprise-3.11/app/scripts/services/deployments.js#L106-L154

• Provide a Roll Back CTA for non-active Replication Controllers associated with Deployment Configs
  
• Roll Back CTA would issue a modal with the same options provided in 3.11