- Shipped
- September 8, 2026 at 12:35 AM UTC
- Author
- Kamo
- Commit
- 656ccb7
The previous commit set nats.jetstream.stream in **************** shipped, deployed — and the new pod still logged NATS stream 'CHAT_MESSAGES' already exists with subjects: [chat.>] because the pod does not read that file. It runs with **************** mounted from k8s/configmap.yaml, so the copy in src/main/resources is the local default and nothing more. The fix was correct and landed nowhere. Worse, VoipNatsStreamConfigTest was green through all of it. A test that reads only the repo copy asserts a property of the developer's machine, and the whole point of that test was to catch a config hole that had no code to look at. It now checks BOTH files and names the offender, and its key lookup is indentation-agnostic — the same keys sit four spaces deeper in the ConfigMap, where a matcher anchored on the other depth finds nothing and reports "not set" for a file that sets it. Verified by removing the block again: the test fails on k8s/configmap.yaml and lists all three orphaned subjects.