Support setting any PAPERLESS_ env variables in values.yaml

[andi0b]

Thanks for this chart, looks very nice!

I would like to set up paperless-ngx with my existing Postgres database and therefore I would need to load the database settings from external configmaps and secrets.

something like:

# values.yaml
paperless:
  env:
    - name: PAPERLESS_DBENGINE
      value: "postgres"
    - name: PAPERLESS_DBHOST
      valueFrom:
         configMapKeyRef:
           name: bring-your-own-db-config
           key: hostname
    - name: PAPERLESS_DBPASS
      valueFrom:
         secretKeyRef:
           name: bring-your-own-db-secret
           key: pass

For other advanced configuration options this would also be a big plus, there are a lot, and I think this chart doesn't need to include them all: https://docs.paperless-ngx.com/configuration/

[psych0d0g]

im contemplating here, for external pgsql i would rather implement the same solution as for mysql, so you could set external database connection information through the config datastructure when not using the subchart's pgsql.
and i would also personally prefer implementing any required env vars in that structure to prevent having to define config options in diffrent areas of the chart's values. maybe within some kind of dynamic "advanced" settings array
From a user perspective that keeps it more simple.

[psych0d0g]

happy that you found a chart which works for you, altough this has nothing to do with the topic of this issue, please stay on topic here :)

[nico151999]

The problem @andi0b was facing is the same reason why I cannot use this chart for my home lab. If the API would be designed the same way the MariaDB credentials are passed I would still find this problematic since I can think of use cases where database secrets are generated by 3rd party operators which require you to follow their secret keys. So not only defining the secret name but also the secret key would be a necessity in many use cases imo. Otherwise, ugly workarounds like duplicating secrets with different key names using jobs or external secrets operator need to be implemented but I would not recommend this. The solution is allowing more flexibility for the chart users imo.

[andi0b]

@nico151999 check my off topic comment, that's probably the solution you're looking for.

[nico151999]

@andi0b I checked it and I ended up using yet another chart (oci://ghcr.io/gabe565/charts/paperless-ngx) but this is only temporary. I'd prefer to see this issue fixed here in this repo. So I don't see this issue resolved unfortunately. Using another chart doesn't improve this one. So I'd kindly like to ask the maintainers if it's desired to make according changes.

[nico151999]

Thanks for opening it again. Let's hope we'll get a statement from the maintainers :)