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

New Issue

decentral1se · 2021-10-21T08:12:29Z

decentral1se commented

2021-10-21 08:12:29 +00:00

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  `abra version dev-07ffa08`

decentral1se added this to the (deleted) 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

decentral1se referenced this issue from a commit

2021-10-21 08:19:45 +00:00

fix: handle chaos mode correctly for deploy

decentral1se closed this issue

2021-10-21 08:19:45 +00:00

Sign in to join this conversation.