The GitHub Actions job "Required Checks" on texera.git/main has succeeded. Run started by GitHub user github-merge-queue[bot] (triggered by github-merge-queue[bot]).
Head commit for run: f14cd3975e7446b77241990b7d573d182d61f88f / ali risheh <[email protected]> fix(k8s): add missing AUTH_JWT_SECRET to values-development.yaml (#6610) ### What changes were proposed in this PR? Adds the `AUTH_JWT_SECRET` environment variable to `bin/k8s/values-development.yaml`. The default `values.yaml` sets `AUTH_JWT_SECRET` inside `texeraEnvVars`, but `values-development.yaml` overrides `texeraEnvVars` as a **whole list**. Helm replaces lists rather than merging them, so a local install with `-f values-development.yaml` silently drops `AUTH_JWT_SECRET` from every Texera service. The computing-unit manager reads this variable directly via `env.get(KEY).get` when launching a Kubernetes computing unit (`ComputingUnitManagingResource.scala`), so the missing value makes **computing-unit creation fail hard**: ``` java.util.NoSuchElementException: None.get POST /api/computing-unit/create HTTP/1.1" 500 ``` Any local Kubernetes deployment following the development values hits this the moment a user tries to create a computing unit. The fix adds the variable with the **same development-only default** already used in `values.yaml`, so all services share one consistent JWT signing secret. ### Any related issues, documentation, discussions? None — standalone bug fix in the development values overlay. Independent of any other in-flight `bin/k8s` work. ### How was this PR tested? Reproduced and verified on a local minikube cluster (`helm install ... -f values-development.yaml`): - **Before:** creating a Kubernetes computing unit returned HTTP 500; the computing-unit manager logged `java.util.NoSuchElementException: None.get`. `kubectl exec` into the manager pod confirmed `AUTH_JWT_SECRET` was unset. - **After** (`helm upgrade` with this change): `AUTH_JWT_SECRET` is present on the manager (and all services), the manager rolled out cleanly, and the `None.get` error no longer occurs. Also confirmed the added value is byte-for-byte identical to the `AUTH_JWT_SECRET` default in `values.yaml`, so development and production use the same variable and the dev overlay stops diverging. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) --------- Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/29779928441 With regards, GitHub Actions via GitBox
