is the recommendation to check the can i deploy against all Pact Foundation #general

is the recommendation to check the can-i-deploy ag...

Phillip Lo

08/02/2023, 4:36 PM

is the recommendation to check the can-i-deploy against all of the environments (non-prod and prod) for consumer PR pipelines or should they only check if the provider has verified their

main

branch and/or the first non-prod env? As in, if the provider has not deployed to production yet with a valid verification, the consumer shouldnt be able to merge their PR with the contract?

Matt (pactflow.io / pact-js / pact-go)

08/02/2023, 9:40 PM

The ideal flow would be a

can-i-merge

check, which https://github.com/pact-foundation/pact_broker-client/issues/138 should address when merged

Matt (pactflow.io / pact-js / pact-go)

08/02/2023, 9:41 PM

I don’t think you need to check against all environments, but it really depends on your workflow. If the consumer goes straight to prod after your PR is merged, then you definitely would want to check it’s compatible with prod (and any intermediate environment you need to ship it through)

Phillip Lo

08/03/2023, 4:25 PM

got it thanks!

Phillip Lo

08/03/2023, 4:27 PM

looks like that PR is already approved so I assume that it should be merged soon?

Matt (pactflow.io / pact-js / pact-go)

08/03/2023, 11:11 PM

Probably 😉

👍 1

Matt (pactflow.io / pact-js / pact-go)

08/30/2023, 2:51 AM

FYI

can-i-merge

is now available in the latest release!

Phillip Lo

09/11/2023, 5:20 PM

nice! just saw this. thanks for the update

🙌 1

Matt (pactflow.io / pact-js / pact-go)

09/11/2023, 10:51 PM

No worries - do please let us know if that helped things for you

3 Views

Open in Slack

Previous Next