hi all, what’s the best practice for migrating connectors across airbyte instances? we currently have two instances: staging and prod. we have a bunch of connectors running on staging and just set up our prod instance, but we don’t know how to migrate. some options i can think of:
- somehow promoting our staging instance to prod — maybe we can copy all the data from our staging env to our prod env? is there a backup/restore option?
- creating new airbyte connectors in prod that point to the same places as staging connectors, and then switching over. what would happen in this case?
- setting up brand new connectors with new destinations in prod — rerunning historical syncs or performing manual backfills
would be great to hear some POVs on these options
When you say “dump from the database” do you mean the airbyte “internal” database?
I would guess it’s something you could automate more easily with an external db right? (would be tricky to do from an ec2 docker compose installation since the db image would move around I would guess)?
So for example you could have a dev external db and a prod external db. Then your CICD pipeline involves triggering a sync of these - dumping from dev to prod.
Could you do this via airbyte itself - having airbyte sync the two? That sounds like it might be circular in logic and prone to problems though.
Hey yeah you can directly take dump from postgres is what I meant
1 Like
Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.