Improve UI rollback check command

Current output of the /chatops run rollback check <environment> looks like this:

Screen_Shot_2021-11-01_at_10.01.41

There are multiple improvement areas:

  1. The message indicates the rollback is unsafe, but the reason for it is unclear. By taking a look at the output, I had assumed it was unsafe due to the migrations, but it was unsafe because there was an ongoing deployment to gprd. If a rollback is deemed unsafe let's highlight the reason.

  2. Let's considered removing the regular migrations section. Regular migrations don't prevent rollbacks, as such they don't add any value to this context. This doesn't apply for post-deployment migrations, amount and specific details should be displayed for those.

  3. Between the SHA's (New, Current, Previous) and the packages, the output shows a lot of information. Additionally showing the package and the coordinated pipeline, as in the proposed solution, could make this output even more verbose. Perhaps we should consider a more succinct version.

Proposal

Let's make the rollback check command succinct by applying the above suggestions.

Final output:

When a deployment is in progress With post-migrations When a deployment is in progress and there are post-migrations
Screen_Shot_2021-11-02_at_11.44.41 Screen_Shot_2021-11-02_at_11.46.46 Screen_Shot_2021-11-02_at_11.41.57
Link to Slack editor Link to Slack Editor Link to Slack editor

Main differences with the current look:

  • The reason behind a rollback deemed unsafe is in a specific section.
  • New, Current and Previous reference to the package and not only to the SHA and they are links to the coordinated pipeline
  • db/post_migrate/ was removed from the post-migrations path, as it's redundant.

Implementation steps

Development log

Edited by Mayra Cabrera