What s the best way to roll out a new pacticipant I ve start Pact Foundation #general

What's the best way to roll out a new pacticipant?...

json

07/13/2022, 7:40 PM

What's the best way to roll out a new pacticipant? I've started building our automation around our pact broker, and I've reached the point where our pipeline will fail pull-request builds if

can-i-deploy

for the given service to deploy to

master

fails... But now I've discovered that when build a new pact provider, it fails

can-i-deploy

because it doesn't exist yet as a pacticipant, and when I add new contract tests to a service, it fails because the contract can't yet be verified, so I'm in a bit of a dependency loop. Is the only way out of this dependency loop to do a one-time suspension of my checks to get my provider merged? Am I maybe doing something wrong? (To be clear, currently my script currently checks to see if the pact provider logic has been implemented in the service and if it has, it runs verifications and then the

can-i-deplay

. It doesn't run any pact stuff if it doesn't see the pact provider logic or a pact file in the service)

json

07/13/2022, 7:55 PM

Actually, as I write this, it occurs to me that maybe the solution lies in just checking if a given service is a pacticipant in the pact broker. Is there an easy way to check that for a given service name?

Timothy Jones

07/14/2022, 1:38 AM

You should always be able to deploy a provider that has no consumers

➕ 1

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

07/14/2022, 3:13 AM

You can definitely check if your provider exists -

:host/pacticipants/:name/

will give you the resource of the application if it exists

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

07/14/2022, 3:15 AM

Tim is right, however with the caveat that can-i-deploy will fail if the application you’re querying doesn’t exist. To create the application, you don’t need a contract - the simplest option is to simply create the application in advance:

curl -X POST <host>/pacticipants -d {"name": "some provider"}

👍 1

json

07/14/2022, 8:15 PM

Perfect, thank you

json

07/14/2022, 8:18 PM

I'm just changing my verifier job so if you pass it a provider name, the first thing it does is check if that provider already exists, and if it doesn't, it creates it (unless you also passed it a pactfile url, which it interprets as an error, because, honestly I'm not even sure how that would happen, but it was probably a mistake)

👍 1

Beth (pactflow.io/Pact Broker/pact-ruby)

07/15/2022, 2:32 PM

it should just work… so it sounds like something got messed up

Beth (pactflow.io/Pact Broker/pact-ruby)

07/15/2022, 2:33 PM

This also might be helpful https://docs.pact.io/pact_nirvana/notes_1

👍 1

json

07/15/2022, 2:33 PM

I think it's just as Matt says: I think it's just can-i-deploy pointing out that my pacticipant doesn't exist in the pact broker yet

json

07/15/2022, 2:34 PM

I just need to improve my pipeline a bit to add the provider as a pacticipant when it's new

json

07/15/2022, 2:35 PM

I reference that pact_nirvana page often, it's very helpful, haha 👍

🙌 1

Beth (pactflow.io/Pact Broker/pact-ruby)

07/15/2022, 2:38 PM

Great to hear.

Beth (pactflow.io/Pact Broker/pact-ruby)

07/15/2022, 2:39 PM

Usually, the consumer adds the pacts for the provider first, and that creates the provider.

json

07/15/2022, 2:40 PM

That makes sense, but since the provider should be able to be developed independently if no consumer depends on it, I wanted to create a path in our pipeline for that as well

Beth (pactflow.io/Pact Broker/pact-ruby)

07/15/2022, 2:40 PM

Cool. Yeah, that page I sent will cover your scenario.

👍 2

json

07/15/2022, 2:43 PM

Oh I hadn't thought of just adding every service-version to the pact broker even without contracts, but that's real smart. Thanks for the tip!

👍 1

👍🏼 1

json

07/15/2022, 7:18 PM

Copy code

docker run --network host pactfoundation/pact-cli broker can-i-deploy --retry-while-unknown=60 --retry-interval=10 --pacticipant=test-service --version=430ff0f --to-environment=master

Computer says no ¯_(ツ)_/¯

No pacts or verifications have been published for version 430ff0f of test-service

Bummer... I thought if a provider had no pacts, it should be safe to deploy? Do I need to specify some other option?

Beth (pactflow.io/Pact Broker/pact-ruby)

07/19/2022, 2:43 PM

If you’re not publishing any pacts or verifications, you need to make the pacticipant version explicitly using

Copy code

pact-broker create-or-update-version --pacticipant ${APPLICATION_NAME} --version ${GIT_SHA} --branch ${GIT_BRANCH}

Beth (pactflow.io/Pact Broker/pact-ruby)

07/19/2022, 2:43 PM

It knows about the pacticipant, but not the version.

json

07/19/2022, 2:46 PM

Oh, I have to publish the version for the provider too, so it can see that it exists and knows that there is no consumer to connect it to?

json

07/19/2022, 2:47 PM

Sorry if you said this already, but do I have to do it as two separate commands, or will

create-or-update-version

also create the pacticipant if it doesn't exist?

✅ 1

json

07/19/2022, 2:52 PM

From that pact_nirvana page you linked above, it looks like the one command may be enough, but I may be mis-reading it

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

07/19/2022, 2:53 PM

yep, it should do both

thank you 1

👍 1

3 Views

Open in Slack

Previous Next