docs: move chartmuseum info into private packages page (#12095)

docs/usage/docker.md

@@ -252,22 +252,3 @@ script:
   - 'echo "module.exports = { hostRules: [ { matchHost: ''eu.gcr.io'', token: ''"$(gcloud auth print-access-token)"'' } ] };" > config.js'
   - renovate $RENOVATE_EXTRA_FLAGS
 ```
-
-#### ChartMuseum
-
-Maybe you're running your own ChartMuseum server to host your private Helm Charts.
-This is how you connect to a private Helm repository:
-
-```js
-module.exports = {
-  hostRules: [
-    {
-      matchHost: 'your.host.io',
-      username: '<your-username>',
-      password: process.env.SELF_HOSTED_HELM_CHARTS_PASSWORD,
-    },
-  ],
-};
-```
-
-If you need to configure per-repository credentials then you can also configure the above within a repository's Renovate config (e.g. `renovate.json`).

docs/usage/getting-started/private-packages.md

@@ -126,6 +126,26 @@ Any `hostRules` with `hostType=packagist` are also included.
 If a `github.com` token is found in `hostRules`, then it is written out to local [GIT*CONFIG*](https://git-scm.com/docs/git-config#Documentation/git-config.txt-GITCONFIGCOUNT) variables prior to running `go` commands.
 The environment variables used are: `GIT_CONFIG_KEY_0=url.https://${token}@github.com/.insteadOf GIT_CONFIG_VALUE_0=https://github.com/ GIT_CONFIG_COUNT=1`.
 
+### helm
+
+Maybe you're running your own ChartMuseum server to host your private Helm Charts.
+This is how you connect to a private Helm repository:
+
+```js
+module.exports = {
+  hostRules: [
+    {
+      matchHost: 'your.host.io',
+      hostType: 'helm'
+      username: '<your-username>',
+      password: process.env.SELF_HOSTED_HELM_CHARTS_PASSWORD,
+    },
+  ],
+};
+```
+
+If you need to configure per-repository credentials then you can also configure the above within a repository's Renovate config (e.g. `renovate.json`).
+
 ### npm
 
 The recommended approaches in order of preference are:

lib/manager/helm-requirements/readme.md

@@ -3,3 +3,5 @@ Renovate supports updating Helm Chart references within `requirements.yaml` file
 If your Helm charts make use of repository Aliases then you will need to configure an `aliases` object in your config to tell Renovate where to look for them.
 
 If you need to change the versioning format, read the [versioning](https://docs.renovatebot.com/modules/versioning/) documentation to learn more.
+
+To learn how to use Helm with private packages, read [private package support, Package Manager Credentials for Artifact Updating, helm](https://docs.renovatebot.com/getting-started/private-packages/#helm).