How to create REST JSON API mocks with Traffic Parrot by recording HTTP requests and responses

Traffic Parrot 5.5.1 released, whats new?

We have just released version 5.5.1. Here is a list of the changes that came with the release:

Features

• Traffic Parrot can now check that gRPC mapping files match proto schema on startup. You can enable this check to prevent startup if mapping files are out of date when compared to the proto schema.
  • The following property enables the feature: trafficparrot.virtualservice.grpc.check.mapping.schema.on.startup=true
  • Currently supports checking gRPC mapping equalToJson request matchers
  • Currently supports checking gRPC mapping response
  • This feature is currently in public beta and is subject to change
  • Please let us know your feedback feedback@trafficparrot.com and help us improve this feature

Changes

• Traffic Parrot now only requires a single port for the UI:
  • trafficparrot.gui.http.port=8080
  The following ports are no longer used by the UI:
  • trafficparrot.virtualservice.http.management.port=8083
  • trafficparrot.virtualservice.jms.management.port=9093
  • trafficparrot.virtualservice.http.port=8081

We also made the following fix in the 5.4.5 release:

Fixes

• gRPC mapping files will now be written with the correct status code of 0 to represent a successful response status. gRPC mapping files with status code 200 will continue to be interpreted as status code 0 to preserve backwards compatibility.

How can I expose multiple port numbers for stubs?

"How can I expose multiple port numbers for stubs, so that each downstream component has an individual port number?"

In Traffic Parrot, you have only one port per Traffic Parrot mock instance. If you would like to use separate ports, you will need to start one Traffic Parrot instance per port.

Let’s discuss the problem you are trying to solve by using multiple ports, please email us at help@trafficparrot.com

We also recommend reading "3 ways to deploy and share virtual services and API mocks"