…iterator, other small tweaks

Ensure that the Postgres image is fully up and running before launching
the broker. This is unlikely to be an issue, but there's hardly any
impact to adding this.

Signed-off-by: JP-Ellis <[email protected]>

In some circumstances, the test will try and connect to the
FastAPI/Flask server before the server has had a chance to be fully
initialised. As these are very lightweight servers, a simple second wait
after the process is spawned should suffice.

Signed-off-by: JP-Ellis <[email protected]>

As the examples are meant to be pedagogical, the docstrings have been
expanded to explain _why_ there is a Filesystem class which only raises `NotImplementedError`.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

There were a few minor issues with the typing annotations:

- `Callable` takes two arguments:
  1. A list of types for the arguments of the function
  2. A single type for the function's return
- Prefer the use of the (more succinct) `|` instead of `Union[...]`

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

As the result is from a single asynchronous message interaction, it
seemed like a more appropriate name. As part of the refactor, the
declaration of the class has been moved and some minor refactoring took
place too.

Signed-off-by: JP-Ellis <[email protected]>

From Pact V4, it is possible for a single Pact to mix different
interaction types; that is, to combine sync/async messages, and HTTP
interactions. As such, I think it is best to keep a single `Pact` class.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Especially in light of the addition of asynchronous messages which only have
one part.

Signed-off-by: JP-Ellis <[email protected]>

The safety concern is handled by the use of `OwnedString`.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

I doubt this will be useful to end-users.

Signed-off-by: JP-Ellis <[email protected]>

also remove the deprecated `message_with_metadata` function from the FFI

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

The functionality is covered by the existing `with_body`

Signed-off-by: JP-Ellis <[email protected]>

Interaction should be done at the Pact level, not at each Interaction.

Signed-off-by: JP-Ellis <[email protected]>

We prefer the use of `InteractionHandle` over `MessageHandle`. The
functionality to add metadata has been added to the FFI, so this
function can make use of this now.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Large commit which implements quite a large number of FFI functions.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

The `interactions` method provides the necessary functionality

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

The provider states don't make sense for pacts, as they are associated
with the individual interactions, as opposed to the pact itself.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Objects generated by the FFI may sometimes be owned by another object,
in which case deleting them when they are out of scope in Python is
invalid. The instantiators for these  classes have been adjusted to take
an optional `owned` keyword argument. If `owned` is `True`, then the
`__del__` function for the class will do nothing.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

The use of `yield from` may sometimes result in the parent instance
being dropped, which then invalidates the underlying iterator. Adding a
final `return` statement (even if it does nothing) ensures that Python
finishes the `yield from` statement first before the function is
finished.

Signed-off-by: JP-Ellis <[email protected]>

The former `get_contents` FFI return the raw body of the interaction,
including matching rules and generators, which aren't very useful when
verifying a message consume. The new methods processes the payload,
replacing the matching rules and generators with values as would be
actually expected by the consumer.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

The exceptions are to be returned during verification.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

The named tuple provides an improved experience for developers.

Signed-off-by: JP-Ellis <[email protected]>

With the other changes in the FFI and Pact Python library, a significant
refactor of the tests was introduced. A few steps were combined, though
by and large the functionality remains the same.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Now that the FFI library supports Windows ARM, we can add it to the
list. Also a minor update to make use of the ARM runners when building
the macOS ARM wheel.

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>

Signed-off-by: JP-Ellis <[email protected]>