(newbie alert) When a consumer needs a new endpoin...
# general
y
(newbie alert) When a consumer needs a new endpoint or some new fields, this should be in close collaboration with the provider right? So before the consumer testing is done, or at least before uploading the contracts. When the provider agrees and implements the contract it can document the new fields/endpoints in for example an open api document. It just that the open api document is not the starting point. Still trying to wrap my head around the whole CDC concept :)
m
So yes, Pact isn’t a replacement for a conversation
🙌 1
💯 2
but also, it can facilitate a good conversation. There is nothing wrong with a consumer creating a branch, putting in what is essentially a request for a change (hey, what if we “added this new field” or “changed the resource to this shape” etc.) and then publishing it. That’s what the branches (selector) feature is for - to be able to delineate between a wip idea and the mainline. Now there is a first class way to communicate that intent, and for the provider team to go “yeah, it looks good and we’ve now implemented the change (because the pact is now green