Yan Bondarenko 15b7092f3a fix(nats): enable JetStream for the generated account ...

With users configured and jetstream.enabled true, the chart enables
JetStream on the server but generates account A without it, so every
JetStream call from those users fails with error 10039, "JetStream not
enabled for account". The generated account now gets jetstream: true
unless it already sets JetStream itself. nats-server matches config keys
case-insensitively and walks the account map in no fixed order, so a
JetStream key in any casing counts as set. Otherwise the account would
carry both keys and the server would apply either one, changing from
restart to restart.

Assisted-by: LLM
Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com>

2026-10-04 10:51:16 +03:00

..

certmanager_test.yaml

test(tests): select documents by identity in absence-only test cases

2026-10-01 22:27:17 +03:00

config_merge_test.yaml

fix(nats): merge config.merge.accounts with the generated accounts map

2026-09-18 13:24:31 +04:00

jetstream_test.yaml

fix(nats): enable JetStream for the generated account

2026-10-04 10:51:16 +03:00

nats_tls_test.yaml

fix(nats): force cluster route useFQDN when TLS enabled to match cert SAN wildcard

2026-05-27 11:19:43 +03:00

tenant_projection_test.yaml

test(nats): pin the trust-anchor sentinel to a single projection entry

2026-08-15 22:40:58 +03:00