How do I configure a Tazama instance deployed via the community Helm chart (or a similar Kubernetes deployment) to actually test rules end-to-end?

A community member tried two approaches after deploying via a community Helm chart: (1) configuring through the Admin Service API - mostly works, but some configuration parameters did not persist; and (2) inserting configuration directly into PostgreSQL via a SQL script (test_config.sql) - worked as a testing workaround but is not recommended for production. Tazama Head of Product pointed to a cleaner path: the tms-configuration repository (github.com/frmscoe/tms-configuration, dev branch), which provides curl-based requests for configuring Tazama via its APIs; this had not yet been tried end-to-end by community members as of July 21, 2026, but is expected to be the more robust approach. Whichever method you use, you'll also need to instantiate the rule containers matching your configuration - straightforward in the Helm chart, just enable the rules you want included. Separately, the tazama Version value in the community chart was updated from a fixed 3.0.0 tag to rc, referring to the 4.0.0 release candidate; Release 4.0.0 has since shipped (promoted to main on July 24, 2026) - check whether the chart has been updated to a fixed 4.0.0 tag. Source: #get-help, July 2026.