OIDC_CUSTOM_PARAMS: ${OIDC_CUSTOM_PARAMS:-} is unquoted. If unset, it can resolve to YAML null (Compose pass-through/omit behavior); if set to {...}, it may be parsed as a YAML map rather than a string. Quote the interpolation or use an explicit empty-string default so the env var is always a string.

Same issue as earlier in the file: leaving ${OIDC_CUSTOM_PARAMS:-} unquoted can resolve to YAML null when unset and can be parsed as a YAML map for {...} values. Quote the interpolation or default explicitly to an empty string so the container consistently receives a string.

Same issue as earlier in the file: ${OIDC_CUSTOM_PARAMS:-} is unquoted; unset can become YAML null (Compose pass-through/omit), and {...} values can be parsed as YAML maps. Quote the interpolation or use an explicit empty-string default to keep the env var value a string.

OIDC_CUSTOM_PARAMS: ${OIDC_CUSTOM_PARAMS:-} is unquoted, which can yield YAML null when unset (Compose pass-through/omit semantics) and YAML map typing when set to {...}. Quote the interpolation or default explicitly to an empty string to keep the env var consistently a string.

Same issue as earlier in the file: this unquoted ${OIDC_CUSTOM_PARAMS:-} can become YAML null when unset and can be parsed as a YAML map when set to {...}, which can lead to Compose pass-through/omit semantics or unexpected stringification. Quote the interpolation or use an explicit empty-string default to ensure a string env var value.

Same issue as earlier in the file: ${OIDC_CUSTOM_PARAMS:-} is unquoted, which can produce YAML null when unset and YAML map typing when set to {...}. Quote the interpolation or use an explicit empty-string default to ensure Compose passes a string env var value.

OIDC_CUSTOM_PARAMS: ${OIDC_CUSTOM_PARAMS:-} is unquoted in a YAML mapping. When the variable is unset this can become a YAML null value (which Compose treats as “take from host env” / omit), and when set to something like {...} it can be parsed as a YAML map rather than a string. To keep Compose behavior consistent and ensure the container always receives a string, quote the interpolation (e.g., wrap the value in double quotes) or use an explicit empty-string default.

OIDC_CUSTOM_PARAMS: ${OIDC_CUSTOM_PARAMS:-} is unquoted in a YAML mapping. When the variable is unset this can become a YAML null value (Compose treats null as pass-through/omit), and when set to {...} it can be parsed as a YAML map instead of a string. Quote the interpolation (wrap in double quotes) or use an explicit empty-string default to ensure the env var value is always a string.

OIDC_CUSTOM_PARAMS: ${OIDC_CUSTOM_PARAMS:-} is unquoted. With the variable unset it can become YAML null (Compose treats as pass-through/omit), and with values like {...} it may be parsed as a YAML map instead of a string. Quote the interpolation or default explicitly to an empty string to keep the env var consistently typed as a string.

OIDC_CUSTOM_PARAMS: ${OIDC_CUSTOM_PARAMS:-} is unquoted in the environment map. This can resolve to YAML null when unset (Compose pass-through/omit semantics) and can be parsed as a YAML map if the value starts with {...}. Quote the interpolation or use an explicit empty-string default to ensure the container receives a string.