Skip to content

fix: Rename disableSessionHandling to authOnly in values.yaml#202

Open
bavarianbidi wants to merge 1 commit into
guerzon:mainfrom
bavarianbidi:patch-1
Open

fix: Rename disableSessionHandling to authOnly in values.yaml#202
bavarianbidi wants to merge 1 commit into
guerzon:mainfrom
bavarianbidi:patch-1

Conversation

@bavarianbidi

Copy link
Copy Markdown

The vaultwarden configmap is already generated with the defined value of the sso.authOnly variable from the values file.

SSO_AUTH_ONLY_NOT_SESSION will get the value which is defined in the values.yaml

SSO_AUTH_ONLY_NOT_SESSION: {{ .Values.sso.authOnly | quote }}

xref: https://github.com/guerzon/vaultwarden/blob/main/charts/vaultwarden/templates/configmap.yaml#L138

This also replaces PR #198.

Note:
Everyone who stumbles over this and the change isn't merged and released yet:
As we do not have a schema for the values file, it's fine to just replace disableSessionHandling with authOnly in your values file. This PR is mainly to fix the gap in the documented values.yaml and help users to safe some time during troubleshooting 😅

The vaultwarden configmap is already generated with the defined value of the `sso.authOnly` variable from the values file.

`SSO_AUTH_ONLY_NOT_SESSION` will get the value which is defined in the `values.yaml`

```
SSO_AUTH_ONLY_NOT_SESSION: {{ .Values.sso.authOnly | quote }}
```

xref: https://github.com/guerzon/vaultwarden/blob/main/charts/vaultwarden/templates/configmap.yaml#L138

This also replaces PR guerzon#198.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant