Skip to content

Releases: pb33f/wiretap

v0.1.20

08 Aug 13:20
Compare
Choose a tag to compare

Changelog

v0.1.19

23 Jul 17:53
Compare
Choose a tag to compare

Changelog

  • 0d7463d OPENAPI: added tests
  • dcf224c OPENAPI: the rewrite header key formatting is odd; let's just make sure all our bases are covered

v0.1.18

04 Jul 14:52
Compare
Choose a tag to compare

Changelog

  • bb3787e Added nill check for path configuration options.

v0.1.17

26 Jun 13:54
Compare
Choose a tag to compare

Changelog

  • 6f57ac5 OPENAPI: accidentally missed a reference to the variable
  • 1ec155c OPENAPI: added better logging to path rewriting. Specifically, if an identifier is provided in a path config, it now ends up in the log message.

v0.1.16

21 Jun 20:01
Compare
Choose a tag to compare

Changelog

  • 637c805 OPENAPI: added redirectId feature to enable users more granular control over rewriting. Additionally, fixed a bug in map ordering
  • ff6d83f OPENAPI: changed rewriteId header value
  • 0579e55 OPENAPI: fixed test caused by changing rewrite header field

v0.1.15

14 Jun 14:04
Compare
Choose a tag to compare

Currently when the response mock engine generates a response using the MockGenerator, the generated responses contain only examples for individual properties that are marked as required, see tests for more details.

The reason why generated responses contain only examples for required properties is a side-effect of using mock generator for validation. While it makes sense for validating required fields for requests, it shouldn't affect the response generation.

Changes:

  • By default, disables the required check on the response mock engine to ensure that all examples for individual properties are used in generated mock responses.
  • Introduces a new configuration option, enable-all-mock-response-fields, to allow only the use of required field examples in the generated mock responses when set to false.

This fix uses pb33f/libopenapi#295


Wiretap just blindly rewrites paths that match any configuration.

Some (poorly written) APIs don't necessarily want to rewrite everything under a specific resource location.

The current way to do this is to add a dummy path rewrite that takes precedence. This is kind of hacky and also doesn't jump over target rewriting.

Changelog

  • 3548ed6 Add tests for property examples usage in mock responses
  • 1357ba0 Added global and local ignore path rewriting support to path configurations.
  • 97a717c Disable required check on response mock engine
  • 0ac01b6 Make mock response field example usage configurable

@jacobm-splunk @martinsirbe

v0.1.14

02 Jun 14:57
Compare
Choose a tag to compare

Changelog

  • dfacb38 Small update to use header variable
  • fb694d0 Wiretap doesn't handle multi-value header keys correctly when writing the response

v0.1.13

13 May 13:15
Compare
Choose a tag to compare

Changelog

  • e283619 Add test case - expected HTTP 204 instead of 200 response
  • effef1f Check and return early when lowest success code is 204

v0.1.12

12 May 17:24
Compare
Choose a tag to compare

Changelog

v0.1.11

02 May 21:56
Compare
Choose a tag to compare

Changelog

  • 3483053 Added mock mode status code override #89