John Ed Alvinez
07/25/2022, 2:53 AM/pacts/provider/{provider}/for-verification
) with this body
{
"consumerVersionSelectors": [],
"includePendingStatus": false
}
what default consumer version selectors does the pact broker use in this scenario if i didn't set it? is it below based on what i can deduce from the pacts it fetched for verification? thanks for your help! π
{
"consumerVersionSelectors": [
{
"mainBranch": true
},
{
"deployedOrReleased": true
}
]
}
tried looking at the docs but could only find the recommended values for consumer version selectors. tried looking at the code too but couldn't find my answer (or i'm just a ruby noob) π
Matt (pactflow.io / pact-js / pact-go)
John Ed Alvinez
07/25/2022, 3:02 AMMatt (pactflow.io / pact-js / pact-go)
John Ed Alvinez
07/25/2022, 3:34 AM{
"consumerVersionSelectors": [
{
"mainBranch": true
},
{
"deployedOrReleased": true
}
]
}
however, sometimes i would see below too.
latest version of some-consumer that has a pact with some-provider (some-commit-hash)
i don't know what setting that corresponds to.
so i wanted to confirm what exactly are the default consumer version selectors since i can't rely on the logs to deduce it since i might miss a setting or two depending on the pacts stored in the broker π
Matt (pactflow.io / pact-js / pact-go)
John Ed Alvinez
07/25/2022, 3:38 AMMatt (pactflow.io / pact-js / pact-go)
Timothy Jones
07/25/2022, 4:12 AMJohn Ed Alvinez
07/26/2022, 12:14 AMbranch
is set when publishing pacts, then criteria are: latest with branch
= main, deployed, released
2. if tag
(deprecated) is set instead of branch
, then criteria are: latest with tag
= main, deployed, released
3. if neither branch
or tag
is set, then criteria are: latest (overall), deployed, releasedTimothy Jones
07/26/2022, 12:28 AMJohn Ed Alvinez
07/26/2022, 3:34 AMBeth (pactflow.io/Pact Broker/pact-ruby)