abra app new and abra app deploy use different checkouts #618

Closed
opened 2024-06-14 19:57:08 +00:00 by iexos · 2 comments

If following the usual instructions of

  • abra app new
  • abra app config
  • abra app deploy

may lead to unintended problems:

  • abra app new creates a config based of the current default branch
  • abra app deploy selects the latest released version for deployment

This may lead to some confusion, if .env.sample has changed in the meantime.

Right now for example the mailman3 and backup-bot-two recipes are affected.

I guess abra app new should also default to the latest release instead.

If following the usual instructions of * `abra app new` * `abra app config` * `abra app deploy` may lead to unintended problems: * `abra app new` creates a config based of the current default branch * `abra app deploy` selects the latest released version for deployment This may lead to some confusion, if `.env.sample` has changed in the meantime. Right now for example the `mailman3` and `backup-bot-two` recipes are affected. I guess `abra app new` should also default to the latest release instead.
iexos added the
bug
label 2024-06-14 19:57:08 +00:00
Owner

Good catch @iexos, deffo a bug!

Good catch @iexos, deffo a bug!
decentral1se added the
abra
label 2024-06-16 18:37:26 +00:00
decentral1se added this to the (deleted) project 2024-06-20 05:45:17 +00:00
Owner

coop-cloud/abra#412 out for review if anyone has spare cycles! This got bumped up as a Critical fix after a quick check with other fedi members.

https://git.coopcloud.tech/coop-cloud/abra/pulls/412 out for review if anyone has spare cycles! This got bumped up as a [Critical fix](https://git.coopcloud.tech/coop-cloud/organising/projects/24) after a quick check with other fedi members.
Sign in to join this conversation.
No description provided.