Worth noting that I'm not 100% what those flags ac...
# pact-neta
Adam Rodger (pact-net)
02/04/2022, 1:07 PMWorth noting that I'm not 100% what those flags actually do though. I assume they only consider provider pacts with a matching branch/tag?
m
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:45 PM
Those flags basically just extra information about the provider doing the verification. Similar to the version
e.g. “version 1234” in “branch X” of “Provider” verified <dynamic set of pacts>.
a
Adam Rodger (pact-net)
02/04/2022, 9:46 PMOh. Shouldn't they be on the publish options method instead of the pact broker method then?
m
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:49 PM
mmm yes, but now I can’t remember where I am
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:49 PM
let me finish this coffee before I confuse myself further 😆
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:50 PM
oh, no, I’m wrong
a
Adam Rodger (pact-net)
02/04/2022, 9:50 PMWhen I split those options out I don't remember them being referenced in the publishing code, but I didn't look in much depth
m
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:50 PM
this is the verification
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:50 PM
there is a consumer selecting that says “matching_branch” (or similar) so it’s about selecting the pacts that match
a
Adam Rodger (pact-net)
02/04/2022, 9:51 PMAh good, because that's pretty much what I said in the PactNet docs 😂
m
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:52 PM
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:52 PM
That was the issue for the reference that requested the support
Matt (pactflow.io / pact-js / pact-go)
02/04/2022, 9:52 PM
(Only the first 2 bullet points are relevant, because we recommend using the CLI for publishing etc.)