rusackas opened a new pull request, #40616:
URL: https://github.com/apache/superset/pull/40616

   ### SUMMARY
   
   Closes #31877
   
   `init.extraContainers` (and all other `extraContainers` fields) were 
rendered with plain `toYaml`, so Go template expressions inside them were 
passed through as literal strings instead of being evaluated. This PR wraps 
each one with `tpl` so template expressions work — matching the existing 
pattern already used for `initContainers`, `extraVolumes`, `command`, and 
`envFromConfigMaps`.
   
   Affected deployments: `supersetNode`, `supersetCeleryBeat`, 
`supersetCeleryFlower`, `supersetWorker`, `supersetWebsockets`, `init` (job).
   
   Bumps chart version `0.15.5 → 0.15.6` per the [chart versioning 
policy](https://github.com/apache/superset/blob/master/helm/superset/README.md#versioning);
 regenerates `helm-docs` README.
   
   Co-authored by @cin (original fix in #31878 — this PR adds the version bump 
and helm-docs that were missing there).
   
   ### BEFORE / AFTER SCREENSHOTS
   
   N/A (Helm template change)
   
   ### TESTING INSTRUCTIONS
   
   - [ ] `helm template` a chart with a `tpl`-using string in 
`supersetNode.extraContainers` and confirm it renders instead of appearing as a 
raw `{{ }}` literal.
   - [ ] Run `helm lint helm/superset` — should pass.
   
   ### ADDITIONAL INFORMATION
   
   - [x] Has associated issue: closes #31877
   - [ ] Required feature flags: N/A
   - [ ] Changes UI: No
   - [ ] Includes DB Migration: No
   - [ ] Introduces new feature or API: No
   - [ ] Removes existing feature or API: No
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to