Hi all, Got a question regarding workflow. So we have Consumer A which has PACTs with Provider B at 3 tags (dev, preprod & prod – we haven’t moved to environments yet). This is working fine. We introduce Provider C which is a provider to Consumer A. We release Provider C to dev as we have set the

failIfNoPactsFound

for the pact:verify and can-i-deploy. Consumer A has a new PACT created to Provider C and released to dev. This works OK. The problem we found is trying to release Provider C to ‘preprod’ where the can-i-deploy says it cannot as there isn’t Consumer A in preprod (which it is true that there isn’t this integration contract between these pacticipants in preprod). I think this though should be a valid workflow (it’s as though it found the integration, so expects the PACT to be available at all tags). We got around it 1st time by deleting the integration, then deploying the provider to all environments before introducing the new Consumer A v Provider C PACT (but think this is a bit of a blunt hammer). It would be good to understand if we are missing something here, and is it something that may be helped through moving to environments? Many thanks in advance.

I think there may be a bug in can-i-deploy for the scenario of introducing a new provider. I've got a failing test case for it here https://github.com/pact-foundation/pact_broker/commit/5bcf6e66d70a5911333366c494a675469f1d0924

Many thanks for your quick response. We have added this variable and can-i-deploy now works in our case, but a couple of things as I understand that this will not fail even if can-i-deploy fails. 1. When can it be removed? Does it need at least 1 consumer to be at each tag that is being checked with can-i-deploy (in our case 'dev', 'preprod', 'prod')? And once there is 1 consumer, others can be added an environment at a time without being expected to be on each one? 2. Is there a bug report on this that we can keep an eye out for any fix? Many thanks

@Paul I believe I've fixed this bug. Can you update to the latest version (2.95.1) and see if you are getting the expected results?

@Beth (pactflow.io/Pact Broker/pact-ruby) We have got an upgrade to the latest version on our backlog at the moment. I'll try to push priority of it again, and let you know when available (its another thing on list to make a business case for moving across to pactflow).

Thanks for letting me know @Paul