Hello, am I able to upload an

asyncapi.yaml

to pactflow? I tried with this command

> pactflow publish-provider-contract ./asyncapi.yaml --provider=KafkaService --provider-app-version=$(git rev-parse HEAD) --broker-base-url=<https://accelerant.pactflow.io> --broker-token=$PACT_BROKER_TOKEN --content-type=application/yaml

Created KafkaService version 00fe84ec138d1cdc0375ac477cb5136fec2b517a
  Next steps:
    Configure the version branch to be the value of your repository branch.
Provider contract published for KafkaService version 00fe84ec138d1cdc0375ac477cb5136fec2b517a.
  View the published provider contract at <https://accelerant.pactflow.io/contracts/bi-directional/provider/KafkaService/version/00fe84ec138d1cdc0375ac477cb5136fec2b517a/provider-contract>
Next steps:
  * Publish test results to show the provider correctly implements the specification.
    The can-i-deploy check for the consumer requires this. See <https://docs.pactflow.io/go/publish-provider-self-verification-results>

and it published it but when i check the pactflow UI I see this...

the cli tool, nor the broker lint the document to ensure it is a valid OpenAPI description on upload. The UI and tooling used in the bi-directional verification will check if it is a valid OpenAPI file, as that is the only currently supported provider contract

oh noes

what gave you that impression, did you read somewhere that it did? it is a feature on our roadmap, and isn’t listed as supported for bi-directional contract testing. you can use message pact, to test the message contents but not the transport. You can also leverage the pact-plugin framework to build a kafka aware plugin if you wished?