helm: fix dbStatementTimeout/dbPoolRecycle/dbPoolMaxOverflow silently dropped when set to 0

[vincere-mori]

Problem

Setting dagsterWebserver.dbStatementTimeout: 0 in Helm values has no effect — the --db-statement-timeout 0 flag never appears in the rendered webserver container args.

Root cause: the template uses {{- with value }} blocks, and Go's text/template treats the integer 0 as falsy. So with 0 skips the block entirely.

0 is a meaningful value for PostgreSQL's statement_timeout — it disables the timeout. Without this fix there is no way to pass --db-statement-timeout 0 through the chart.

The same bug affects dbPoolRecycle and dbPoolMaxOverflow.

A secondary issue: large integers like 2147483647 (max int32) are rendered as 2.147483647e+09 because Helm parses YAML integers as float64 and the default formatter switches to scientific notation at large values.

Reproduce

# values.yaml
dagsterWebserver:
  dbStatementTimeout: 0

helm template dagster dagster/dagster -f values.yaml | grep db-statement-timeout
# expected: --db-statement-timeout 0
# actual:   (no output — flag is absent)

Fix

Replace {{- with value }} with {{- if not (kindIs "invalid" value) }}. The kindIs "invalid" predicate returns true only for nil/null values, correctly distinguishing between "not set" (null/omitted) and "set to zero". Piping through int64 ensures decimal formatting for all integer magnitudes.

Applied to all three flags: dbStatementTimeout, dbPoolRecycle, dbPoolMaxOverflow.

Fixes #33821

[greptile-apps]

Greptile Summary

This PR fixes a silent flag-suppression bug in the Dagster Helm chart where dbStatementTimeout, dbPoolRecycle, and dbPoolMaxOverflow were dropped from the rendered webserver command when set to 0, because Go's text/template treats integer 0 as falsy inside a with block. It also prevents large integers (e.g. max int32) from being rendered in scientific notation.

• Template fix (_helpers.tpl): Replaces {{- with value }} with {{- if not (kindIs \"invalid\" value) }} for all three DB flags, and pipes each value through | int64 to guarantee decimal output.
• Tests (test_dagit.py): Adds test_webserver_db_flags_zero_values and test_webserver_db_flags_large_values to cover the two previously broken cases across all three flags.

Confidence Score: 5/5

Targeted, well-understood fix with new tests that cover the exact failure modes; no regressions expected.

The change is narrow: three lines in one template helper and two new test cases. The kindIs invalid idiom is the standard Helm/Sprig pattern for nil-vs-zero discrimination, and the int64 pipe cleanly handles float64-to-integer formatting. Existing passing tests exercise positive values; the new tests cover 0 and max-int32. No surrounding logic is altered.

No files require special attention.

Important Files Changed

Filename	Overview
helm/dagster/templates/helpers/_helpers.tpl	Replaces with (falsy-skips zero) with kindIs "invalid" guard and int64 pipe for three DB flag helpers — correctly emits 0 and formats large integers in decimal.
helm/dagster/schema/schema_tests/test_dagit.py	Adds two new parameterized tests covering zero-value flags and max-int32 large-value flags; coverage is correct and symmetric across all three DB flags.

_{Reviews (2): Last reviewed commit: "test(helm): add zero-value and large-int..." | Re-trigger Greptile}