https://pact.io logo
Join Slack
Powered by
Hi here, I noticed that when pact broker calls the...
# pact-broker
d
Hi here, I noticed that when pact broker calls the provider webhook, it passed a couple of 
PACT_CONSUMER_TAG
e.g.: 
PACT_CONSUMER_TAG="bugfix_COPS-8853-orion-reenable-contract, bugfix_COPS-8853-orion-reenable-contract-SNAPSHOT"
, looks like 
@VersionSelector(consumer = "orion", tag = "${pactConsumerTag}")
could not really handle multiple tags in that format, is that expected?
b
The version selector is not meant for that purpose
you should have an option to pass in a pact URL.
d
for example?
b
Sorry, I'm not familiar with the JVM options, but ask in the pact-jvm channel.
have a look in the provider section of the docs.pact.io page for your language
👀 1
d
so multiple tag were passed by the broker is expected
b
yes.
but you're not meant to do with them what you're currently doing.
to trigger a build via a webhook, you should use the pact URL
d
I will see how that works in jvm
👍🏼 1
looks like it's 
pact.filter.pacturl
, is that right? @Beth (pactflow.io/Pact Broker/pact-ruby)?
what's the version in the url suppose to be? provider version or consumer version?
Copy code
mvn pact:verify -Dpact.filter.consumers='Foo Web Client' -Dpact.filter.pacturl=<https://test.pact.dius.com.au/pacts/provider/Activity%20Service/consumer/Foo%20Web%20Client/version/1.0.1>
b
@Deven Chen the URL that comes from the webhook is actually a permalink to the content of the pact, and doesn't contain the consumer version. It includes the pact version.
I don't know if that's the right option - you'll need to ask in the pact-jvm channel, sorry.
2 Views
Open in Slack
PreviousNext
Powered by