For HTTP you can:
- Add/Edit HTTP mappings
- Import and export HTTP mappings (see above the supported formats for HTTP)
- Use the Management APIs
- Use GIT with trafficparrot.virtualservice.trafficFilesRootUrl
- Create the JSON mapping files directly on the disk (see mappings and __files directories after you have created a service)
Traffic Parrot has support for the following formats to import HTTP:
- WireMock 2.x mappings in ZIP format
- Swagger 1.x and 2.x
- OpenAPI 2.x and 3.x
- RAML 0.8
For Native IBM MQ MQ you can:
- Add the mappings manually (copy paste message body etc.)
- Use GIT with trafficparrot.virtualservice.trafficFilesRootUrl
- Use the management APIs
- Create the JSON mapping files directly on disk (ibm-mq-mappings directory)
No comments:
Post a Comment