Getting below error while pulling up the helm repo

helm repo add casdoor https://hub.docker.com/repository/docker/casbin/casdoor-helm-charts

[ec2-user@ip-10-101-6-41 casdoor]$ helm repo add casdoor https://hub.docker.com/repository/docker/casbin/casdoor-helm-charts Error: looks like "https://hub.docker.com/repository/docker/casbin/casdoor-helm-charts" is not a valid chart repository or cannot be reached: error converting YAML to JSON: yaml: line 21: mapping values are not allowed in this context

The index.yaml is missing from the repository. It originally existed in casdoor but was removed once the helm components were migrated to this repo. The index.yaml is an important file as it simplifies the helm installation process for developers without needing to manually download the helm chart to their machines. We should add this file back in and similar to how Chart.yaml is updated by the CI, the index.yaml should also be updated accordingly. Currently, this workflow generates the index.yaml but it's never committed to git. A quick solution would be to update casdoor workflow to commit the index.yaml and push up to docker hub. This repo would no longer require a workflow directory then

@MichaelSp The Chart version is incorrect in this repo. Also, the commit message has a typo

Commit Message
chor(helm): bump helm charts appVersion to v1.495.0

The chor should be chore

See latest commit

Given this casdoor-helm-chart has its own version number (right now is 0.4.3), it's good practice for this repo only to have Semantic-Release like how our other repos do (like casdoor). So people can clearly track the versions and have an easy-to-follow changelog

kubectl logs -f pod/casdoor-58f45c79f4-shv9z -n casdoor
panic: pq: no pg_hba.conf entry for host "10.224.0.76", user "postgres", database "postgres", no encryption

goroutine 1 [running]:
github.com/casdoor/casdoor/object.(*Ormer).createTable(0xc0008d7000)
/go/src/casdoor/object/ormer.go:293 +0xaa5
github.com/casdoor/casdoor/object.CreateTables()
/go/src/casdoor/object/ormer.go:114 +0x3a
main.main()
/go/src/casdoor/main.go:36 +0x35

Thanks you for help
https://access.crunchydata.com/documentation/postgres-operator/4.4.0/advanced/custom-configuration/

The instructions in the docs are wrong (https://casdoor.org/docs/basic/try-with-helm/), after some messing around I discovered that the published version on oci://registry-1.docker.io/casbin/casdoor-helm-charts is 0.4.5, which however is very different from what's published here.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing name property in package.json.

The package.json's name property is required in order to publish a package to the npm registry.

Please make sure to add a valid name for your package in your package.json.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The committer in this repo is wrong: https://github.com/casdoor/casdoor-helm/commits/master/

Why wrong?

• No avatar
• No link

The correct example is: https://github.com/casdoor/casdoor.github.io/commits/master/