You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1334 removed oidcProxy.enabled from values.yaml but left the template
reading it, so it fell through to its default of false. Every OIDC
variable sits behind that gate, which means a values file written to the
contract this design documents renders with the whole auth block
missing and the container fails at start on absent configuration. The
render fixture only passed because it still carried the flag.
The service has no auth_enabled field any more -- test_auth asserts
that -- so nothing consumed OSMO_MCP_AUTH_ENABLED either. Authentication
is not a mode, and the chart now says so: the gate, the environment
variable and the flag in the fixture are gone, and the required messages
name MCP rather than a proxy that could be switched off.
Guarded by a render assertion that the auth block renders from a fixture
carrying no enable flag, and that no enable switch is emitted.
{{- $oidcAccessTokenRequiredScope = required "services.mcp.oidcProxy.oidc.accessTokenRequiredScope is required when the OIDC proxy is enabled" $oidcProxy.oidc.accessTokenRequiredScope }}
39
+
{{- $oidcAccessTokenRequiredScope = required "services.mcp.oidcProxy.oidc.accessTokenRequiredScope is required when MCP is enabled" $oidcProxy.oidc.accessTokenRequiredScope }}
42
40
{{- if not (regexMatch "^[A-Za-z0-9:._~-]{1,128}$" $oidcAccessTokenRequiredScope) }}
43
41
{{- fail "services.mcp.oidcProxy.oidc.accessTokenRequiredScope must be one non-empty scope" }}
0 commit comments