mirrors/external-secrets
1
0
Fork 0
mirror of https://github.com/external-secrets/external-secrets.git synced 2024-12-14 11:57:59 +00:00
Code Activity

Fix typo in pushsecrets docs (#2998)

Browse source
This commit is contained in:
Matúš Ferech 2024-01-04 15:28:05 +01:00 committed by GitHub
parent 0fbc4a8340
commit 0ac250dd2d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/pushsecrets.md
View file

@ -13,7 +13,7 @@ By default, the secret created in the secret provided will not be deleted even a
An interesting use case for `kind=PushSecret` is backing up your current secret from one provider to another one.
Imagine you have your secrets in GCP and you want to back them up in Azure Key Vault. You would then create a `SecretStore` for each provider, and an `ExternalSecret` to pull the secrets from GCP. This will generetae `kind=Secret` in your cluster that you can use as the source of a `PushSecret` configured with the Azure `SecretStore`.
Imagine you have your secrets in GCP and you want to back them up in Azure Key Vault. You would then create a `SecretStore` for each provider, and an `ExternalSecret` to pull the secrets from GCP. This will generate a `kind=Secret` in your cluster that you can use as the source of a `PushSecret` configured with the Azure `SecretStore`.
![PushSecretBackup](../pictures/diagrams-pushsecret-backup.png)