Hi, I had a question about whether there is an override for this behaviour. For a provider, I have been running can-i-deploy as a way of checking if verifications exist between my current branch and ‘main’ branch consumers and then through the deployment lifecycle checking if there are verifications between environments. I recently cleared down contracts to test what would happen with custom webhooks when the consumer runs can-i-deploy to trigger the provider (it worked fine). The problem I had was when the provider was deployed to a later environment than the consumer, where no contracts existed between them. I can understand the usecase of failing can-i-deploy if the contracts were unverified as interactions would be required but what about where the are no consumers in the environment for a provider. is that a breaking case? So my question is…is there a flag to say “don’t fail if there are no consumers of this tag/environment” so it only fails if the contract has changed and there has previously been a verification for the tag and/or environment but not for this latest version

@James P take a look at the IgnoreNoPactsToVerify annotation - could probably be what you need

Thanks Basu, I’ve tried the IgnoreNoPactsToVerify in the past for provider verification but it doesn’t seem to affect the can-i-deploy pact broker cli

Can I deploy does not require the consumer to be present to deploy the provider. It should work fine.