Docs missing how to upgrade app for recipes published by others #450
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#450
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I want to use existing recipes and deploy updates, when they are available. I couldn't find any documentation for that.
The workflow I found is smth like this:
abra app ls -S
abra app upgrade <domain>
Is this reliable? Are there better ways?
Basically, yes. We this this one-liner to get a review of all upgradeable apps:
abra app ls -S -m | jq '.[].apps | select( . != null )[] | [ .appName, .upgrade ] | @csv'
Ideally, major changes which require action from operators would be listed as recipe release notes, displayed on the point of running
abra app upgrade
-- in practice, not all of them are, your mileage may vary.Lastly, as I think mentioned in Co-op Cloud Tech, the
kadabra
daemon can help with notifying about, or even installing, app updates: https://docs.coopcloud.tech/operators/tutorial/#automatic-upgrades