Improve the layout of the "diff table" when push/pull/status with an environment

When doing a push/pull/status command within the CLI the diff table can sometimes seem a little cryptic. What has changed and what will be changed by completing the command isn't always very clear and changes depending on the command run:


I would prefer if the single "no change/update/create/delete" label included a direction or explanation of which version was being updated/created/deleted etc.

In order to instil confidence in what is about to happen compared to what I think I've asked to happen is really important. Doing a push to Live can be quite a stressful experience when all you see is "delete" or "update" for an item you didn't touch!

I was thinking that each line could be something like this showing which one is the freshest version for each entry, I can't think of a good design but this is the intent I would like to be able to infer from the table:

* "Auth - franchisemanager - Live is newer (changed at x/y/z) than local (changed at a/b/c), continuing will overwrite/update your local copy"
* "Function - customerImport - Doesnt exist on Live but Local does so it will be created on Live"
* "Function - webFormSubmission2 - Live has deleted this so it will be removed from Local"

I've never seen the Provider plugin be anything over than awscloudformation so could we lose that to make some more room for something more descriptive for the important stuff? If not what are the options for this column and when might they change, why is this information of note and who to?

Additionally is there a way to know if a user hasn't done a pull yet there are new things up on the cloud before they push? Could we keep a timestamp or hash of when they last synced up and warn them if a pull should be done before hand. Without this and when we didn't know better this used to cause me and my work mate to get in unknown states. Ideally we should limit that.