Support rollback/new in deployment version handling logic #84

New Issue

decentral1se · 2021-03-02T12:10:34Z

decentral1se commented

2021-03-02 12:10:34 +00:00

Follows from #82.

Only a change in the version is recognized, not if that change is a new forwards deployment (new version) or a rollback (back to a previous version). We need to make the difference and adjust the output to show for that.

Follows from https://git.autonomic.zone/coop-cloud/abra/issues/82. Only a change in the version is recognized, not if that change is a new forwards deployment (new version) or a rollback (back to a previous version). We need to make the difference and adjust the output to show for that.

decentral1se added the

bug

label 2021-03-02 12:10:34 +00:00

decentral1se self-assigned this 2021-03-02 12:11:36 +00:00

decentral1se added this to the Beta release milestone 2021-03-02 12:17:44 +00:00

decentral1se referenced this issue

2021-03-04 08:57:49 +00:00

Add "abra rollback" to drop back to a last working version #76

decentral1se commented

2021-03-04 15:28:35 +00:00

Actually, wait a second, this is not needed because rollback goes backwards and deploy goes forwards!

Actually, wait a second, this is not needed because `rollback` goes backwards and `deploy` goes forwards!