Might be a stupid question but I've had a look aro...
# pactflow
b
Might be a stupid question but I've had a look around the docs and couldn't find anything. What are the options around configuring multiple brokers for consumers? (an existing pact broker and a newer pactflow instance) Or is there a way to transition to pactflow while keeping the history of verifications etc?
y
No this is an excellent question. I have posed it to the team. I am unsure if there is a way at the moment (although have tabled a couple of possible options) Also you have got me wondering if there are cases of users with multiple OSS brokers, and how they manage them (if they do exist)
m
I believe we can take a dump of your current broker, and use that as a basis for your Pactflow account - i.e. start your account from the OSS and presto, you have Pactflow with all of your data.
then you would need to point your builds from the old OSS broker to Pactflow (it would require an outage as far as your existing setup is concerned, so could do it out of band potentially to reduce disruption).
Alternatively, the idea of a “backup” where you shadow all (or, many) requests to pactflow also is possible, but we don’t have a solution for it atm
Depending on what data you need, it might be a few API calls to fetch and pump in the things you need
b
Thanks for the replies! I think the multiple brokers for a consumer would be preferable right now as we just want to test out pactflow (bi-directional etc) before fully committing. Can you let me know @Yousaf Nabi (pactflow.io) if you hear anything?
Although knowing how to switch over would still be useful! Is there anything I can read up about on that @Matt (pactflow.io / pact-js / pact-go)?
b
The simplest way to do it is duplicate the publish/verify commands in your build and run them in parallel until everything has been pushed out to prod, then turn off the old one.
👍 2