hi! `pending pact` s again :slightly_smiling_face:...
# general
d
hi!
pending pact
s again 🙂 from docs
1. Consumer publishes a new pact with tag
main
that has a new unsupported interaction in it.
what if i want to amend existing interaction (like enrich message with 1 more field) ? c-i-d in this case says, that pact is failed. do I do/understand something wrong ? so in this case i need 2 interactions ? 1 for old message, 1 for enriched?
m
That would be a new pact for pending purposes
d
but question was more - if i as a consumer altering existing interaction - should it became pending or failing ?
m
It’s a new pact version, in that it has new requirements in it. It will be pending as far as the provider is concerned (subject to the usual pending calculations)
if the provider can’t support it (pending enabled or otherwise) the consumer’s
can-i-deploy
will still fail
👍 1
d
has a new unsupported interaction in it.
then this doesn’t counts as new 🙂
m
what do you mean, sorry?
d
Copy code
hi! pending pact s again 
 from docs

Consumer publishes a new pact with tag main that has a new unsupported interaction in it.
some wording could be updated in docs
as it could be read as
only new interactions could be pending
m
No, the pending status is at the pact level, not the interaction level.
If the contents of the pact changes at all, it is a new pact (version) and if pending is enabled on the provider side, will be treating as a pending pact
d
thats clear 🙂
🙌 1