Implement stack version and update logic #82

New Issue

decentral1se · 2021-02-17T23:05:09Z

decentral1se commented

2021-02-17 23:05:09 +00:00

Following coop-cloud/organising#34, the idea might be then to use docker tag to tag a successfuly deployed ..._app container (we really do need that naming convention then!) with the ABRA_TYPE_... version metadata.

Then we have containers running with version metadata that we control.

Following step is then to do a diff of that version metadata on the running container in the stack with the app repo specified metadata when running the next deploy.

My cautious self is leaning towards always bailing out on abra <app> deploy when seeing a version update. Then giving a warning and asking to pass --update if OK or something. Unsure.

Following https://git.autonomic.zone/coop-cloud/organising/issues/34, the idea might be then to use `docker tag` to tag a successfuly deployed `..._app` container (we really do need that naming convention then!) with the `ABRA_TYPE_...` version metadata. Then we have containers running with version metadata that we control. Following step is then to do a diff of that version metadata on the running container in the stack with the app repo specified metadata when running the next deploy. My cautious self is leaning towards always bailing out on `abra <app> deploy` when seeing a version update. Then giving a warning and asking to pass `--update` if OK or something. Unsure.

decentral1se added the

enhancement

design

labels 2021-02-17 23:05:09 +00:00

decentral1se self-assigned this 2021-02-17 23:05:09 +00:00

decentral1se commented

2021-02-24 11:50:08 +00:00

coop-cloud/organising#34 (comment) seems to be looking sensible! Might try to adjust the deploy logic to just add those lables as a first step next time I get a chance.

https://git.autonomic.zone/coop-cloud/organising/issues/34#issuecomment-3876 seems to be looking sensible! Might try to adjust the deploy logic to just add those lables as a first step next time I get a chance.

3wordchant commented

2021-02-24 13:27:51 +00:00

Excellent stuff.

My cautious self is leaning towards always bailing out on abra <app> deploy when seeing a version update. Then giving a warning and asking to pass --update if OK or something. Unsure.

Sounds good, maybe we add a dedicated version check as well? Possibly add to abra app ls and/or abra app <app> check?

Excellent stuff. > My cautious self is leaning towards always bailing out on `abra <app> deploy` when seeing a version update. Then giving a warning and asking to pass `--update` if OK or something. Unsure. Sounds good, maybe we add a dedicated version check as well? Possibly add to `abra app ls` and/or `abra app <app> check`?

👍 1

decentral1se referenced this issue from a commit

2021-03-02 11:05:26 +00:00

Add version and digest showing

decentral1se referenced this issue from a commit

2021-03-02 12:07:09 +00:00

Support basic version checking

decentral1se closed this issue

2021-03-02 12:07:09 +00:00

decentral1se referenced this issue

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

Support rollback/new in deployment version handling logic #84