I'm trying to set multiple values in given namespace for pact metadata but always only get the last value I set. I'm using

pact-python

, but it passes its arguments along to

lib.pactffi_with_pact_metadata(

. My example is this:

pact.with_metadata('namespace', {'var_1': 'value_1', 'var_2': 'value_2'})

which breaks down into multiple calls as listed above, but the resulting pact file only contains:

"metadata": {
    "namespace": {
      "var_2": "value_2"
    },
    ...

You will want to use the v2 function I think

pactffi_message_with_metadata_v2

PactFfi::MessageConsumer.with_metadata_v2(message, "namespace",'{"var_1":"value_1","var_2":"value_2"}')

"metadata": {
        "contentType": "application/json",
        "namespace": {
          "var_1": "value_1",
          "var_2": "value_2"
        }
      },

interesting... that's gonna require a change to the clients I think

I think the v2 func was introduced to allow for metadata matchers using the integration json format.

It doesn't look like either

pact-js

or

pact-python

use the

v2

function. Guess I'll see about getting that added to those 🙂. Thanks for the info!

Ahh right, I imagine that will be implemented in the same way as the message_metadata(v1) func was, and probably suffers the same fate. we won’t need the matchers here, but may want to process json payloads with nested keys

We have a number of different ways our services interact with one another, and I was hoping to use metadata to track that information. I could probably also do it with tags, but that significantly complicates the publishing process for services that have several different pacts. It felt easier to just use metadata since that gets written directly into the pact file itself.

I don’t think has enough args btw

pact.with_metadata('namespace', {'var_1': 'value_1', 'var_2': 'value_2'})

/**
 * Sets the additional metadata on the Pact file. Common uses are to add the client library details such as the name and version
 * Returns false if the interaction or Pact can't be modified (i.e. the mock server for it has already started)
 *
 * * `pact` - Handle to a Pact model
 * * `namespace` - the top level metadat key to set any key values on
 * * `name` - the key to set
 * * `value` - the value to set
 */
bool pactffi_with_pact_metadata(PactHandle pact,
                                const char *namespace_,
                                const char *name,
                                const char *value);

The python library breaks that dict down into individual calls to

pactffi_with_pact_metadata

ahh yeah, it must be a bug, it is only picking up the last value, where the namespace is not unique

oh cool - thank you!