rancher
/
fleet-docs
mirror of https://github.com/rancher/fleet-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix case mistake in helmRepoURLRegex property

This commit is contained in:
David Warburton 2023-07-12 10:00:11 -04:00 committed by Corentin Néau
parent b1faa46011
commit b8b90da81c
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/gitrepo-add.md
View File

@ -104,7 +104,7 @@ Just like with SSH, reference the secret in your GitRepo resource via `clientSec
:::warning
The credentials will be used unconditionally for all Helm repositories referenced by the gitrepo resource.
Make sure you don't leak credentials by mixing public and private repositories. Use [different helm credentials for each path](#use-different-helm-credentials-for-each-path),
or split them into different gitrepos, or use `helmRepoUrlRegex` to limit the scope of credentials to certain servers.
or split them into different gitrepos, or use `helmRepoURLRegex` to limit the scope of credentials to certain servers.
:::
For a private Helm repo, users can reference a secret with the following keys:

2
docs/ref-gitrepo.md
View File

@ -53,7 +53,7 @@ spec:
# Helm credentials from helmSecretName will be used if the helm repository url matches this regular expression.
# Credentials will always be used if it is empty or not provided
#
# helmRepoUrlRegex: https://charts.rancher.io/*
# helmRepoURLRegex: https://charts.rancher.io/*
#
# To add additional ca-bundle for self-signed certs, caBundle can be
# filled with base64 encoded pem data. For example:

2
versioned_docs/version-0.6/gitrepo-add.md
View File

@ -151,7 +151,7 @@ Just like with SSH, reference the secret in your GitRepo resource via `clientSec
:::warning
The credentials will be used unconditionally for all Helm repositories referenced by the gitrepo resource.
Make sure you don't leak credentials by mixing public and private repositories. Split them into different gitrepos, or use
`helmRepoUrlRegex` to limit the scope of credentials to certain servers.
`helmRepoURLRegex` to limit the scope of credentials to certain servers.
:::
For a private Helm repo, users can reference a secret with the following keys:

2
versioned_docs/version-0.6/ref-gitrepo.md
View File

@ -53,7 +53,7 @@ spec:
# Helm credentials from helmSecretName will be used if the helm repository url matches this regular expression.
# Credentials will always be used if it is empty or not provided
#
# helmRepoUrlRegex: https://charts.rancher.io/*
# helmRepoURLRegex: https://charts.rancher.io/*
#
# To add additional ca-bundle for self-signed certs, caBundle can be
# filled with base64 encoded pem data. For example:

2
versioned_docs/version-0.7/gitrepo-add.md
View File

@ -105,7 +105,7 @@ Just like with SSH, reference the secret in your GitRepo resource via `clientSec
:::warning
The credentials will be used unconditionally for all Helm repositories referenced by the gitrepo resource.
Make sure you don't leak credentials by mixing public and private repositories. Use [different helm credentials for each path](#use-different-helm-credentials-for-each-path),
or split them into different gitrepos, or use `helmRepoUrlRegex` to limit the scope of credentials to certain servers.
or split them into different gitrepos, or use `helmRepoURLRegex` to limit the scope of credentials to certain servers.
:::
For a private Helm repo, users can reference a secret with the following keys:

2
versioned_docs/version-0.7/ref-gitrepo.md
View File

@ -53,7 +53,7 @@ spec:
# Helm credentials from helmSecretName will be used if the helm repository url matches this regular expression.
# Credentials will always be used if it is empty or not provided
#
# helmRepoUrlRegex: https://charts.rancher.io/*
# helmRepoURLRegex: https://charts.rancher.io/*
#
# To add additional ca-bundle for self-signed certs, caBundle can be
# filled with base64 encoded pem data. For example: