tanishqgandhi1908 opened a new pull request, #8472: URL: https://github.com/apache/texera/pull/8472
### What changes were proposed in this PR? Six environment variables were read with `Option.get`, so a deployment missing any of them failed with `None.get`. Dropwizard shows that as "There was an error processing your request" — no variable named, no cause, and six candidates to check. Every missing variable is now listed at once, as a 503. All at once because when these are missing they are usually all missing: the helm chart supplies all six, so they are present together or absent together. ``` Before: one unset -> 500 "There was an error processing your request" After: any unset -> 503 naming every missing variable ``` Also fixes the default computing-unit image, which named a personal repository that is gone. It now points at what this repository publishes, which is what the helm chart already sets. **No change for any working deployment.** When the six variables are set the map built is identical. The helm chart always sets `KUBERNETES_IMAGE_NAME`, so the default only affects a service run outside the chart — where today no unit starts at all. ### Any related issues, documentation, discussions? Closes #8467 Part of #8466 ### How was this PR tested? Three new tests for `requiredComputingUnitEnv` (all set, one missing, all missing), and the existing default-image assertion updated. ``` sbt "ComputingUnitManagingService/testOnly org.apache.texera.service.resource.ComputingUnitManagingResourceSpec" "Config/testOnly org.apache.texera.common.config.KubernetesConfigSpec" ComputingUnitManagingResourceSpec 34 passed, 0 failed KubernetesConfigSpec 6 passed, 0 failed ``` ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
