EvgheniiShipilov

> Shouldn't this issue be created in the Pact project? Do you mean there's a separate Spring Pact project? If so could you please point me to the correct repo?...

I'm not quite sure what has to be fixed. According to specification both destination and routing key are specified using metadata. Destination is currently taken directly from metadata. Routing key...

I'm not an expert, but my opinion is that yes, some changes have to be applied to Spring Cloud Contract. I see that as adding a new metadata key for...

Does the specification support routing keys in any form? Ex. RabbitMQ would require specifying the destination exchange and routing key separately.

> Yes, it supports it via metadata (otherwise we'd need queue specific fields in the spec, which is not ideal). You'll need to look at the language specific docs for...