Backupbot Revolution #23
Merged
moritz
merged 31 commits from 2023-10-09 10:54:22 +00:00
backupbot_revolution into main
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
backupbot revolution
Done
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
moritz
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/backup-bot-two#23
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
First quick pass, looking great! Great work!
@@ -45,0 +80,4 @@Add your `SSH_KEY` as docker secret:```abra app secret insert <app_name> ssh_key v1 """$(cat backupkey)"""Unwanted newline?
Unfortunately this newline-hack is required, else the ssh-key is not accepted.
Will it break anything on our existing backup setups if we merge this? Is a migration path needed? @moritz
@moritz ran into this error while trying to set things up:
Would it also be an idea to try and set up some tests for this while we're here? I can imagine we'll be changing the code as we go. Idk if you'd like to do that in Python or we could try something simple like the integration suite for
abra(manually for the time being...).I broke it through some silly code formatting. Yeah some tests would prevent this.
For migration the repository variables need to be merged, I pushed a release note:
a2aec9b59eThis way the backup script is independent of the repository type.
@moritz any chance you could resolve the merge conflicts? Unsure I've got the right changeset resolving myself while testing / implementing the
abraside of things. Thanks!Oh right, they're diverging 🤔
I think you need to undelete
backup.shfor backwards compat while we're still transitioning?Should the cronjob then also only run backup.sh? At the moment I don't see any issues for backwards compat apart the migration steps inside
release/next. Maybe we shouldn't release the next version until it's not tested well.0cc9c3598dtobb1237f9adI rebased everything to resolve the merge confict