Hey, This page <https://docs.pact.io/pact_broker/...
# pactflow
e
Hey, This page https://docs.pact.io/pact_broker/recording_deployments_and_releases#application-instances says that application instances shouldn't be used for blue/green or other long running deployments (eg canary). But it doesn't say what should be used instead... We're currently running with two consumers - Foo.Stable and Foo.Canary - but not sure if this is advisable or not
m
This message contains interactive elements.
For blue/green standard
record-deployment
is
(sorry, I saw your other post earlier today but just didn’t get a chance to read the specific question and respond)
e
So TL;DR: With blue/green it's normal to have two consumers e.g
MyConsumer-Blue
&
MyConsumer-Green
?
m
Ah! No, same consumer just a different version
e
But if we record a deployment to the environment, that removes the previously deployed version from the environment
m
Correct. Given the advice on the above page, you should only do that once the cutover is in place though. 1-6 hours is an awfully long time though.
e
1-6 hours is an awfully long time though
It's enough time to see sufficent real-world usage and compare it to "stable" in parallel to be confident we haven't regressed 🙂
👍 1
m
We’re currently running with two consumers - Foo.Stable and Foo.Canary - but not sure if this is advisable or not
How does the consumer know it’s hitting the stable or canary version of the provider? Usually, this is transparent to consumers
e
Sorry - we're not canary releasing our provider. We're canary releasing the consumer
m
oh sorry. That was my bad assumption
I think in your case you could consider it a “long-running” deployment. But having two applications is probably not the end of the world either
e
Right - in which case, the feature-request still stands 😉
😆 1
m
haha yep