Inconsistency in tagging pacts while publishing to broker
See original GitHub issueWe are trying to tag pact files, but the only first found pact file is tagged.
import pact from '@pact-foundation/pact-node';
const opts = {
pactFilesOrDirs: [${__dirname}/../../../pacts/*/],
pactBroker: brokerurl,
pactBrokerUsername: brokerusername,
pactBrokerPassword: brokerpassword,
consumerVersion: '1.0.0',
tags : ['prod', 'test']
};
pact.publishPacts(opts)
.then(() => {})
.catch(e => {
console.error('Pact contract publishing failed: ', e);
process.exit(1);
});
Any idea how to solve this issue?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Inconsistency in tagging pacts while publishing to broker #77
We are trying to tag pact files, but the only first found pact file is tagged. import pact from '@pact-foundation/pact-node';.
Read more >Tags | Pact Docs
Tag with the branch name when you publish pacts or verification results, and tag ... See Versioning in the Pact Broker for more...
Read more >Final Rule: Publication or Submission of Quotations Without ...
broker-dealers to continue to rely on the piggyback exception to publish quotations for an issuer in certain instances when the issuer's ...
Read more >Recovering agents in the inconsistent state - TechDocs
Log on to the management console as an administrator. · Go to. Assets > Agent Install . · Select the agents which you...
Read more >FX GLOBAL CODE
In this example, while the Client and executing dealer are responsible for resolving the trade discrepancy, they do need help from the Prime...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We have multiple providers for single consumer, for that we are creating pact files as below to distinguish each other. consumer1-navigation-service consumer1-store-service, consumer2-add-to-cart, consumer2-recommendation-service consumer3-recommendation-service consumer3-srp-svc
When try to publish these, as pact-broker got consumer2 as first as below log shows,
So only, consumer2-add-to-cart, consumer2-recommendation-service are tagged but not others as below
To prove this hypothesis, we tried to have only below pacts consumer1-navigation-service consumer1-store-service, consumer3-recommendation-service consumer3-srp-svc
When try to publish these, as pact-broker got consumer1 as first as log shows
So only, consumer1-navigation-service , consumer1-store-service are tagged but not other as below,
Please help us @mefellows
Thank you, we modified all pacts to same consumer name as per the suggestion and we were able to tag them all.