Post-deploy abra.sh hooks #235

New Issue

decentral1se · 2021-11-05T09:06:36Z

decentral1se commented

2021-11-05 09:06:36 +00:00

Describe the problem to be solved

e.g. when you deploy Nextcloud and would like to have some apps installed automagically.

Describe the solution you would like

abra_postdeploy_hook (or whatever) function is read from abra.sh and ran if present after a deploy. Potentially configurable via --hooks (or whatever) flags on deploy?

## Describe the problem to be solved e.g. when you deploy Nextcloud and would like to have some apps installed automagically. ## Describe the solution you would like `abra_postdeploy_hook` (or whatever) function is read from `abra.sh` and ran if present after a deploy. Potentially configurable via `--hooks` (or whatever) flags on `deploy`?

decentral1se added this to the Command-line tool sustainability milestone 2021-11-05 09:06:36 +00:00

decentral1se added the

enhancement

abra

labels 2021-11-05 09:06:36 +00:00

decentral1se added this to the Beta release (software) project 2021-11-05 09:06:36 +00:00

decentral1se removed this from the Command-line tool sustainability milestone 2021-12-21 23:26:19 +00:00

decentral1se modified the project from Beta release (software) to Spicing abra up

2021-12-21 23:26:22 +00:00

decentral1se commented

2022-03-11 11:08:12 +00:00

Centralising on #301.

Centralising on https://git.coopcloud.tech/coop-cloud/organising/issues/301.

decentral1se closed this issue

2022-03-11 11:08:12 +00:00

moritz commented

2023-04-12 14:25:24 +00:00

I reopen this, because abra app cmd #301 still has to be run manually after each deploy or upgrade if necessary.

My proposal is to introduce two new env variables: POST_DEPLOY_CMDS=<container> <command> <arguments>|<container> <command2> <arguments2>|... and POST_UPGRADE_CMDS. These variables contain abra.sh commands that should be executed after each deployment/upgrade.
For example for nextcloud:

POST_UPGRADE_CMDS="app run_occ db:add-missing-indices|app run_occ db:convert-filecache-bigint"
POST_DEPLOY_CMDS="app set_default_quota|app install_onlyoffice"

Abra should wait until all health checks are successful and than automagically run these commands.
This requires working health checks and #437 so it won't abort before the health checks are finished.

I reopen this, because `abra app cmd` #301 still has to be run manually after each deploy or upgrade if necessary. My proposal is to introduce two new env variables: `POST_DEPLOY_CMDS=<container> <command> <arguments>|<container> <command2> <arguments2>|...` and `POST_UPGRADE_CMDS`. These variables contain abra.sh commands that should be executed after each deployment/upgrade. For example for nextcloud: - `POST_UPGRADE_CMDS="app run_occ db:add-missing-indices|app run_occ db:convert-filecache-bigint"` - `POST_DEPLOY_CMDS="app set_default_quota|app install_onlyoffice"` Abra should wait until all health checks are successful and than automagically run these commands. This requires working health checks and https://git.coopcloud.tech/coop-cloud/organising/issues/437 so it won't abort before the health checks are finished.

👀 1 🎉 1

moritz reopened this issue

2023-04-12 14:25:24 +00:00

3wordchant commented

2023-04-12 15:58:07 +00:00

Would love to see this, thanks @moritz!