I’m about to migrate drone from internal SQLite to a fresh AWS RDS database. I don’t care about preserving job history. However will I lose any github integrations such as repo toggle switch state, or the signed repo keys used to clone, etc?
Basically wondering if I use the same auth keys if everything will just work or if I’ll have to set up anything new or clean out anything old.
or the signed repo keys used to clone
Drone uses the oauth token to clone. As long as your installation uses the exact same github client_id and client_secret you should be fine.
will I lose any github integrations such as repo toggle switch state […] will I have to set up anything new or clean out anything old?
Drone uses a per-repository key for signing and verifying hooks. This means that if you switch databases you will lose the per-repository key, and therefore need to re-enable your repositories and replace the existing hooks.
This is something that you should be able to automate.
You could snapshot a list of all enabled repositories, upgrade drone, and then re-enable all repositories from the command line. When you enable it will remove and replace old hooks. Something like the below script (disclaimer: script not verified)
# step 1: save a list of active repositories
drone repo ls > repos.txt
# step 2: upgrade your drone server
# step 3: re-activate your repositories
cat repos.txt | xargs -I{} drone repo add {}