All installs miss the recipe label, kadabra can't do its work #403

New Issue

decentral1se · 2023-02-10T14:43:34Z

decentral1se commented

2023-02-10 14:43:34 +00:00

If I run kadabra on an existing co-op cloud install, none of the deployed apps have the recipe label. is there a way kadabra could auto-discover and apply? Perhaps this could be a separate command? Unsure of the API interface but it seems like we'd want to do something for this instead of asking operators to re-deploy lots of apps?

Also, running kadabra on the server today gives no feedback. When I pass -d then I see it's missing all the labels but erroring out with a "nothing to do" message might also be good?

If I run `kadabra` on an existing co-op cloud install, none of the deployed apps have the recipe label. is there a way `kadabra` could auto-discover and apply? Perhaps this could be a separate command? Unsure of the API interface but it seems like we'd want to do something for this instead of asking operators to re-deploy lots of apps? Also, running `kadabra` on the server today gives no feedback. When I pass `-d` then I see it's missing all the labels but erroring out with a "nothing to do" message might also be good?

decentral1se added the

bug

label 2023-02-10 14:43:34 +00:00

decentral1se commented

2023-02-10 14:44:20 +00:00

Maybe abra could learn how to label deployments? abra app label <domain> <label>? But this would still make operators need to write a script to label everything 🤔 Unsure.

Maybe `abra` could learn how to label deployments? `abra app label <domain> <label>`? But this would still make operators need to write a script to label everything 🤔 Unsure.

decentral1se added the

kadabra

label 2023-02-10 14:45:44 +00:00

decentral1se referenced this issue

2023-02-10 14:48:46 +00:00

kadabra doesn't guard for incorrect arguments? #404

moritz commented

2023-04-14 15:13:38 +00:00

I don't know a way around redeploying / upgrading the apps. I introduced this label because kadabra is not able to figure out which recipe the deployed apps are based on.

I'm not sure about the verbosity of kadabra. If it is run regularly by a cronjob, it should notify only if it upgrades an app or if it failed unexpectedly.
If it notifies for every disabled or non-update-able app at each execution that would spam the inboxes. Therefor I thought passing -d is enough to get this information.

I don't know a way around redeploying / upgrading the apps. I introduced this label because `kadabra` is not able to figure out which recipe the deployed apps are based on. I'm not sure about the verbosity of `kadabra`. If it is run regularly by a cronjob, it should notify only if it upgrades an app or if it failed unexpectedly. If it notifies for every disabled or non-update-able app at each execution that would spam the inboxes. Therefor I thought passing `-d` is enough to get this information.

decentral1se commented

2023-04-14 16:53:22 +00:00

Sounds good! Yeh I guess it is just a transition stage, people will have to undeploy/deploy. Thanks!

decentral1se closed this issue

2023-04-14 16:53:23 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 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#403