[helm] dagit.logLevel (#7862)

CHANGES.md

@@ -24,6 +24,7 @@
 - [dagster-dbt] The `load_assets_from_dbt_project()` and `load_assets_from_dbt_manifest()` utilities now have a `use_build_command` parameter. If this flag is set, when materializing your dbt assets, Dagster will use the `dbt build` command instead of `dbt run`. Any tests run during this process will be represented with AssetObservation events attached to the relevant assets. For more information on `dbt build`, see the [dbt docs](https://docs.getdbt.com/reference/commands/build).
 - [dagster-dbt] If a dbt project successfully runs some models and then fails, AssetMaterializations will now be generated for the successful models.
 - [dagster-snowflake] The new Snowflake IO manager, which you can create using `build_snowflake_io_manager` offers a way to store assets and op outputs in Snowflake. The `PandasSnowflakeTypeHandler` stores Pandas `DataFrame`s in Snowflake.
+- [helm] `dagit.logLevel` has been added to values.yaml to access the newly added dagit --log-level cli option.
 
 ### Bugfixes
 

helm/dagster/schema/schema/charts/dagster/subschema/dagit.py

@@ -39,6 +39,7 @@ class Dagit(BaseModel):
     annotations: kubernetes.Annotations
     enableReadOnly: bool
     dbStatementTimeout: Optional[int]
+    logLevel: Optional[str]
 
     class Config:
         extra = Extra.forbid

helm/dagster/schema/schema_tests/test_dagit.py

@@ -190,6 +190,23 @@ def test_dagit_db_statement_timeout(deployment_template: HelmTemplate):
     assert f"--db-statement-timeout {db_statement_timeout_ms}" in command
 
 
+def test_dagit_log_level(deployment_template: HelmTemplate):
+    log_level = "trace"
+    helm_values = DagsterHelmValues.construct(dagit=Dagit.construct(logLevel=log_level))
+
+    dagit_deployments = deployment_template.render(helm_values)
+    command = " ".join(dagit_deployments[0].spec.template.spec.containers[0].command)
+
+    assert f"--log-level {log_level}" in command
+
+    helm_values = DagsterHelmValues.construct(dagit=Dagit.construct())
+
+    dagit_deployments = deployment_template.render(helm_values)
+    command = " ".join(dagit_deployments[0].spec.template.spec.containers[0].command)
+
+    assert "--log-level" not in command
+
+
 def test_dagit_labels(deployment_template: HelmTemplate):
     deployment_labels = {"deployment_label": "label"}
     pod_labels = {"pod_label": "label"}

helm/dagster/templates/helpers/_helpers.tpl

@@ -43,6 +43,7 @@ If release name contains chart name it will be used as a full name.
 dagit -h 0.0.0.0 -p {{ .Values.dagit.service.port }}
 {{- if $userDeployments.enabled }} -w /dagster-workspace/workspace.yaml {{- end -}}
 {{- with .Values.dagit.dbStatementTimeout }} --db-statement-timeout {{ . }} {{- end -}}
+{{- with .Values.dagit.logLevel }} --log-level {{ . }} {{- end -}}
 {{- if .dagitReadOnly }} --read-only {{- end -}}
 {{- end -}}
 

helm/dagster/values.yaml

@@ -61,6 +61,9 @@ dagit:
   # The timeout in milliseconds to set on database statements sent to the Dagster instance.
   dbStatementTimeout: ~
 
+  # The log level of the uvicorn web server, defaults to warning if not set
+  logLevel: ~
+
   # Additional environment variables to set.
   # A Kubernetes ConfigMap will be created with these environment variables. See:
   # https://kubernetes.io/docs/concepts/configuration/configmap/