Skip to content
This repository was archived by the owner on Nov 9, 2025. It is now read-only.
This repository was archived by the owner on Nov 9, 2025. It is now read-only.

Enabling auth lead to badly-formated deployment manifest #41

@celliern

Description

@celliern

While setting romm.config.auth.enabled to true, helm complain during the YAML to JSON conversion.

A closer look show that the envs in deployment looks like that :

          env:- name: ROMM_AUTH_ENABLED
            value: "true"- name: ROMM_AUTH_USERNAME
            valueFrom:
              secretKeyRef:
                name: romm-credentials
                key: romm-user
          - name: ROMM_AUTH_PASSWORD
            valueFrom:
              secretKeyRef:
                name: romm-credentials
                key: romm-pass- name: ROMM_AUTH_SECRET_KEY
            valueFrom:
              secretKeyRef:
                name: romm-shared-secret
                key: auth-secret

Where it should look something like that :

          env:
          - name: ROMM_AUTH_ENABLED
            value: "true"
          - name: ROMM_AUTH_USERNAME
            valueFrom:
              secretKeyRef:
                name: romm-credentials
                key: romm-user
          - name: ROMM_AUTH_PASSWORD
            valueFrom:
              secretKeyRef:
                name: romm-credentials
                key: romm-pass- name: ROMM_AUTH_SECRET_KEY
            valueFrom:
              secretKeyRef:
                name: romm-shared-secret
                key: auth-secret

I suspect that the ident is not being correctly dealt with in the deployment template around line 40-48.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions