Home Explore Help
Sign In
logic855
/
helm-external-secrets
mirror of https://github.com/external-secrets/external-secrets
1
0
Fork 0
Files Issues 0 Wiki
Browse Source

Update docs/guides-getallsecrets.md

Co-authored-by: Moritz Johner <moolen@users.noreply.github.com>
Gustavo Fernandes de Carvalho 4 years ago
parent
f687c1e520
commit
0d62ffad8a
1 changed files with 1 additions and 1 deletions
Unified View Show Diff Stats
  1. 1 1
      docs/guides-getallsecrets.md

+ 1 - 1
docs/guides-getallsecrets.md
View File 

@@ -1,6 +1,6 @@
 
 # Fetching information from multiple secrets
 
 # Fetching information from multiple secrets
 
 
 
-In some use cases, it might be impractical to bundle all sensistive information into a single secret, or even it is not possible to fully know a given secret name. In such cases, it is possible that an user might need to sync multiple secrets from an external provider into a single Kubernetes Secret. This is possible to be done in external-secrets with the `dataFrom.find` option.
 
+In some use cases, it might be impractical to bundle all sensitive information into a single secret, or even it is not possible to fully know a given secret name. In such cases, it is possible that an user might need to sync multiple secrets from an external provider into a single Kubernetes Secret. This is possible to be done in external-secrets with the `dataFrom.find` option.
 
 
 
 !!! note
 
 !!! note
 
     The secret's contents as defined in the provider are going to be stored in the kubernetes secret as a single key. Currently, it is not possible to apply any decoding Strategy during a find operation.
 
     The secret's contents as defined in the provider are going to be stored in the kubernetes secret as a single key. Currently, it is not possible to apply any decoding Strategy during a find operation.