fmjstudios / helm

🪖 A collection of MIT-licensed Helm Charts
MIT License
7 stars 10 forks source link

[Linkwarden] SSO Configuration invalid due to the Schema requiring an array with items of type string #2

Closed CronixZero closed 3 months ago

CronixZero commented 4 months ago

Name and Version

fmjstudios/linkwarden 0.2.0

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Setup SSO as recommended
    linkwarden.auth.sso:
    - provider: "authentik"
    customName: "SSO"
    issuer: "authentik"
    existingSecret: "linkwarden-sso-secret"
  2. Run ´helm template`
  3. Doesn't work due to values.schema.json

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

Unable to create application: application spec for linkwarden is invalid: InvalidSpecError: Unable to generate manifests in linkwarden: rpc error: code = Unknown desc = Manifest generation error (cached): `kustomize build <path to cached source>/linkwarden --enable-helm` failed exit status 1: Error: Error: values don't meet the specifications of the schema(s) in the following chart(s):
linkwarden:
- linkwarden.auth.sso.0: Invalid type. Expected: string, given: object

: unable to run: 'helm template linkwarden <path to cached source>/linkwarden/charts/linkwarden-0.2.0/linkwarden --namespace linkwarden -f /tmp/kustomize-helm-123460339/linkwarden-kustomize-values.yaml' with env=[HELM_CONFIG_HOME=/tmp/kustomize-helm-123460339/helm HELM_CACHE_HOME=/tmp/kustomize-helm-123460339/helm/.cache HELM_DATA_HOME=/tmp/kustomize-helm-123460339/helm/.data] (is 'helm' installed?): exit status 1

Additional information

No response

strelok899 commented 4 months ago

same issue here

strelok899 commented 4 months ago

@FMJdev i am having the same issue if this pr help i would be glad that you can employ it

Andre15711 commented 3 months ago

When will Version 0.2.1 release?

FMJdev commented 3 months ago

Hey guys sorry for the long wait. I have just published a new minor 0.3.0 which fixes the issue.