Hi <#CLS16AVEE|>. My project has newly introduced ...
# pactflow
j
Hi #CLS16AVEE. My project has newly introduced pactflow, and we are trying to figure out naming conventions etc, to make the integration work for all the different products and teams (it is a large project with many different products and teams within those products, as well as different service providers - so not always an easy task). A suggestion for the naming convention for the provider name in the pacts, was to attatch the stage (dev/int/prod etc) as part of the name, to make it possible to have different versions of a pact on different stages. I have a feeling that this is possible to do without adding it to the provider name, it is also available as a tag, and I think it must somehow be a part of your versioning concept. So my question: does pactflow offer a way to handle different versions of pacts on different stages?
m
> have a feeling that this is possible to do without adding it to the provider name, Yep! I’d suggest not using stage names in the provider name, because that’s the whole point of recording deployments
j
Thank you Matt. I will suggest we use this approach 🙂
One follow up question, is it only possible to record deployments using the pact broker CLI? We are currently using the maven plugin...
m
yes, or the API
https://smartbear.portal.swaggerhub.com/pactflow/default/getting-started (It’s the PactFlow API, but deployments are the same as the open source)
You could always write your own Maven plugin using these APIs