Chaos deploy still picks version and bails on unstaged changes #210

Closed
opened 2021-10-21 08:12:29 +00:00 by decentral1se · 0 comments
Owner

Describe the current behavior

➜  coop-cloud-apps (main) ✗ abra app deploy --force --chaos foobar.com
WARN[0001] 'foobar.com' already deployed but continuing (--force) 
INFO[0001] choosing '3.0.0+15.0.2' as version to deploy 
FATA[0001] 'keycloak' has locally unstaged changes  

In this case, I just wanted my local unstaged changes to be deployed.

Steps to reproduce

abra app deploy --force --chaos <app>

Describe the expected behavior

It deploys in chaos mode. Unstaged local changes go out.

Any idea how this might be fixed?

Rework deploy logic.

Additional information

abra version dev-07ffa08

## Describe the current behavior ``` ➜ coop-cloud-apps (main) ✗ abra app deploy --force --chaos foobar.com WARN[0001] 'foobar.com' already deployed but continuing (--force) INFO[0001] choosing '3.0.0+15.0.2' as version to deploy FATA[0001] 'keycloak' has locally unstaged changes ``` In this case, I just wanted my local unstaged changes to be deployed. ## Steps to reproduce `abra app deploy --force --chaos <app>` ## Describe the expected behavior It deploys in chaos mode. Unstaged local changes go out. ## Any idea how this might be fixed? Rework deploy logic. ## Additional information <!-- run "abra -v" on the command-line --> `abra version dev-07ffa08`
decentral1se added this to the Command-line tool sustainability milestone 2021-10-21 08:12:29 +00:00
decentral1se added the
bug
abra
labels 2021-10-21 08:12:29 +00:00
decentral1se added this to the Beta release (software) project 2021-10-21 08:12:29 +00:00
Sign in to join this conversation.
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#210
No description provided.