Hey folks. We've stumbled upon an issue we're not ...
# general
s
Hey folks. We've stumbled upon an issue we're not sure how to tackle correctly. Our consumer service recently added a dependency on a new provider, but that dependency is optional. Ie if the new provider is deployed in the environment, make calls to it, if not, fallback to the old provider. This behavior is controlled by a feature flag, so it's the same application build that can operate in two modes; this also means that the new provider might already be deployed in the environment, but consumer would still use the old one based on the team's decision. What's the right way to approach this with pact and
can-i-deploy
? If we're going to deploy a consumer version to the environment without the new provider, we want to skip checking the contract with new provider. Is there a way to mark a contract as applicable to a specific environment only?
🤔 1
m
I think the best advice is to compare to the “feature toggles” article: https://docs.pact.io/pact_broker/tags#using-tags-with-feature-toggles-instead-of-feature-branches This could do with some updating/testing (ideally tags should be replaced with branches, but we need to confirm if that approach is equivalent in behaviour)
đź§  1
thankyou 2 1