Closed applejag closed 2 years ago
It's failing the install-chart
because the secret created by postgres isn't found by the wharf-api. Further investigation is needed, as it clearly does find it when testing locally.
It's failing the
install-chart
because the secret created by postgres isn't found by the wharf-api. Further investigation is needed, as it clearly does find it when testing locally.
Idea: it's not being deployed with name "wharf-aino", so the secret has a different name
I did some digging into Helm's chart-testing (ct) util, and it does not support changing the release name (https://github.com/helm/chart-testing/blob/ab83f064a372c46938b0017a1fe4373b786e4ec0/pkg/chart/chart.go#L205-L219) There's also an existing feature request on the topic: https://github.com/helm/chart-testing/issues/310
As we cannot use .Values...
in the values.yaml
, we cannot set the password to be read automatically from a secret generated by the postgres chart. This is a deeper feature request on Helm, that I warn about that you do not go down that rabbit hole. There's no such feature on the horizon, so just stick with working around it.
charts/wharf-*/CHANGELOG.md
file, according to docs: https://iver-wharf.github.io/#/development/changelogs/writing-changelogs (but without version dates nor WIP versions)charts/wharf-*/Chart.yml
Summary
wharf-aino
Motivation
Makes it easier to get started with Wharf.