John Fallows
John Fallows
Topic filter wildcard syntax in `mqtt` uses `+` and `#`. - https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901241 We should definitely enforce this in `zilla.yaml` schema for both `mqtt` and `mqtt-kafka` bindings, to get a more...
[zilla-dump-pr-341.zip](https://github.com/aklivity/zilla/files/12325261/zilla-dump-pr-341.zip)
[zilla-dump-issue-371.zip](https://github.com/aklivity/zilla/files/12372492/zilla-dump-issue-371.zip)
Replaced by #679
This can happen if `zilla dump` cannot keep up with `zilla` without being "lapped" in one or more of the ring buffers.
> [@jfallows](https://github.com/jfallows), could you please assign this issue to me? Done. ✅
@ankitk-me This looks good and okay to proceed as proposed above. However, bear in mind that at some point we'll likely want to defer to `guard` to inject credentials, using...
Suggest we use existing OpenAPI terminology for `required` headers, instead of `mandatory`. ``` http_server: type: http kind: server options: requests: - path: /api/v1/.* headers: x-custom-header: required: true model: string ```...
@ankitk-me Btw, can the same effect be achieved by using `json` model with `schema` that has `type: string` and `required: true` without any syntax changes?
Given that we currently only run the validation on headers that are present, we need to consider backward compatibility when introducing `required` headers. This means that if we choose to...