Skip to content

Feat/add mask fields policies - #7195

Open
fabianrbz wants to merge 24 commits into
mask-field-policyfrom
feat/add-mask-fields-policies
Open

fabianrbz wants to merge 24 commits into
mask-field-policyfrom
feat/add-mask-fields-policies

Conversation

@fabianrbz

Copy link
Copy Markdown
Contributor

Description

Add mask field policies and a tool to validate the event-gateway-policy examples (+ a fix for automated-tests)

Fixes #issue

Preview Links

Checklist

  • Tested how-to docs. If not, note why here.
  • All pages contain metadata.
  • Any new docs link to existing docs.
  • All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
  • Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.
  • Every page has a description entry in frontmatter.
  • Add new pages to the product documentation index (if applicable).

Extraction now follows the same pattern, files that are meant to be
skipped are skipeed both when using --product and not.
Tool that validates existing policy examples agains the corresponding
schema in the api spec
@fabianrbz
fabianrbz requested a review from a team as a code owner September 10, 2026 13:31
Comment thread app/_how-tos/event-gateway/kong-identity-oauth.md
Update minimum version for event-gateway to 1.1.0.
Adds a standalone Liquid block/drop pair that renders the canonical
Event Gateway quickstart instructions (script, exported gateway ID,
demo-only note), with an optional env map and test-step declaration.
No page calls it yet; that's tickets 03-05.
…quid

Renames {% quickstart %} to {% event_gateway_quickstart %} and moves
the curl command construction out of the Ruby drop and into
snippet.md, iterating over the env map directly. The drop is now
limited to parsing env/section and building the test-step payload,
with the script URL, network name, and control-plane name hardcoded
in the template since this block is Event Gateway-specific.
Adds a `quickstart` step handler that composes a page's env flags onto
the runtime's base quickstart command, runs it, and persists every
`export NAME=VALUE` line it prints for later steps. The Konnect Event
Gateway runtime gains that base command plus a reset-time wipe of files
a previous test file generated.
…d block

Renders the OTel quickstart command from {% event_gateway_quickstart %}
with the four OTel env flags, so the copy-pasted command and the
harness-run command come from the same source.
Uses the event_gateway_quickstart block with section: none so the
prerequisite's wording can no longer drift from the other call sites,
while staying inert to the test harness (no data-test-step emitted).
Content-shape assertions for the curl command (env formatting, special
characters) belong at the snippet.md render seam, not the Liquid block
seam, matching the claude-code snippet_spec.rb pattern. The block spec
keeps only block-wiring behavior: test-declaration emission, malformed
YAML, and markdown output_format. Also drops a leftover byebug
breakpoint and its now-incorrect expectation.
Make the docker-compose-start.md prereq blocks and have the extractor
run them, not all the how-tos need this so running them always was
causing issues with  clusters  defined in specific how-tos.
cycle

A file that runs the quickstart itself (a `quickstart` liquid tag in its steps)
provisions its own gateway, and usually its own cluster too. The runtime only provisions
a kafka cluster and quickstart script when the file declares no quickstart of its own.
and sleep for 5s after creating the egw to give it time to be ready
…r how-to

`openssl x509 -req` produces a version 1 certificate when it receives no
extensions. Event Gateway rejects a v1 client certificate with
"invalid peer certificate: UnsupportedCertVersion", so the mTLS handshake
to the broker fails and kafkactl reports "run out of available brokers".

Sign the client certificate with an extension file, as the broker
certificates already do, to make it a v3 certificate. OpenSSL 3.2 and later
add key identifier extensions by default, which hides the problem, but
OpenSSL 3.0 is still the version on Ubuntu 24.04, Debian 12 and RHEL 9.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant