Traffic Parrot 5.66.0 is out. Here are the four things worth knowing about it, and the full release notes carry the rest.
A mapping explorer, and documentation for working with mocks as files
Writing a mapping file by hand means knowing which keys it can carry and what each one accepts. The new mapping explorer, linked from Help and from each mapping editor, lists every key a mapping file can carry for HTTP, gRPC, JMS, native IBM® MQ and file messages, with its description, allowed values and an example. It searches keys and matcher names, checks a pasted mapping with the check trafficparrot validate runs, naming each problem at the key it concerns, and builds a skeleton mapping to download. For people who would rather edit the files than use the web user interface, Working with files is the new place to start: writing a mapping by hand, the file layout, and each user interface action beside the file it writes and the API call that does the same.
Usage metrics for your own Prometheus and Grafana
With trafficparrot.telemetry.enabled=true an instance serves GET /api/metrics on its user interface port, behind the same login as the user interface: the mappings it has loaded, the requests it serves by protocol and outcome, the recordings it starts and the HTTP mappings created, updated and deleted while it runs, every series labelled with the team and project tags you give the instance. No metric name or label value is taken from traffic. The new Tools, Monitoring page shows the scrape URL with an example Prometheus scrape configuration, and offers a Grafana dashboard as a download. See Monitoring with Prometheus and Grafana.
HTTP mocks in Default can stay on the default ports while you switch virtual services
Set trafficparrot.virtualservice.defaultPorts.followSelection to false and restart: the default HTTP and HTTPS ports then always serve Default, and selecting a virtual service decides only which one the pages show and edit. For example, HTTP mocks in Default run next to one JMS virtual service per queue manager, switched between without the HTTP mocks stopping. Nothing changes unless you set it. See Select Virtual Service.
A mock OAuth2/OIDC provider can be scaffolded from the web user interface
The HTTP Add/Edit page has a New OAuth2/OIDC mock button. Its form takes the mock's name, issuer, public base URL, audience, token lifetime, extra claims and client credentials, all optional, and Scaffold writes the three mappings, a discovery document, a JWKS and a client_credentials token endpoint, and lists their URLs to give the system under test. See Scaffolding a mock.
Also in this release
- Credential headers can be redacted to a hash token while recording, so one value stays linked wherever it appears in the saved mapping.
equalToJsoncan match a field set tonulland a missing field with each other.- A file over the in-memory limit is consumed, and written as a response, without being read into memory.
- Saving a mapping in the HTTP or gRPC mapping editor keeps the metadata and response transformers the form does not show.
trafficparrot validatechecks the HTTP mapping files in subdirectories too.- gRPC mappings have a JSON schema of their own.
The release notes list every feature, change and fix in 5.66.0. To try it, start a trial.
