Reinhard Nägele
Reinhard Nägele
This is not supported. Any reason why you need this?
When I became a maintainer I learned it was best practice to auto-generate passwords and have told folks to follow this pattern. I never really questioned this but am not...
cc @kubernetes/charts-maintainers
There seems to be support specifically for `build-helper-maven-plugin`. However, there are lots of plugins which generate sources and add them to the classpath, usually under `target/generated-sources`. In this case, `build-helper-maven-plugin`...
BuildKit supports specifying multiple tags. You can build and push to multiple registries with one command.
Git repo should be `my-charts`, not the full URL.
This is already the case. You don't have to have the packages around. The existing index file is downloaded from the repo and the new stuff is merged in.
The tool reported `No chart changes detected` so it didn't do anything.
Wouldn't labels be better suited for this? We could explicitly create namespaces and add labels like so: ```yaml app.kubernetes.io/name: my-namespace app.kubernetes.io/instance: my-release app.kubernetes.io/managed-by: github.com/helm/chart-testing ```
chart-testing can lint and/or install/test your charts.