What's the issue?

The --db-statement-timeout flag for the Dagster webserver cannot be set to 0 via Helm values. The template uses {{- with ... }}, which Go's text/template treats as falsy for the integer 0, so the flag is omitted from the rendered command. 0 is a meaningful value for PostgreSQL's statement_timeout (it disables the timeout), so this prevents users from disabling the statement timeout through the chart.
The values.schema.json also constrains the field to integer | null, which blocks the usual string-quoting workaround.

Also, using a large integer like 2147483647 instead renders as 2.147483647e+09 because Helm parses YAML numbers into Go as float64 and the default formatter switches to scientific notation.

What did you expect to happen?

When dbStatementTimeout: 0 is set explicitly, the rendered command should include --db-statement-timeout 0, propagating to PostgreSQL's statement_timeout = 0 (no timeout). The flag should only be omitted when the value is null / unset.

How to reproduce?

1. Install the chart with the following in values.yaml:

  dagsterWebserver:
     dbStatementTimeout: 0

2. Render the chart:

helm template dagster dagster/dagster -f values.yaml | grep db-statement-timeout

3. Observe that --db-statement-timeout does not appear in the rendered webserver container args.

Dagster version

1.12.20

Deployment type

Dagster Helm chart

Deployment details

Chart: dagster/dagster (version: 1.12.20)
Kubernetes: v1.33.9+rke2r1

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.