Просмотр исходного кода

fix: root providers under a provider field

This is needed for easy-to-use CR validation, see external-secrets/external-secrets#9
Moritz Johner 5 лет назад
Родитель
Сommit
62608c9fa8
1 измененных файлов с 22 добавлено и 19 удалено
  1. 22 19
      Spec.md

+ 22 - 19
Spec.md

@@ -222,25 +222,28 @@ spec:
   # Optional
   controller: dev
 
-  # AWSSM configures this store to sync secrets using AWS Secret Manager provider
-  awssm:
-    # Auth defines the information necessary to authenticate against AWS by 
-    # getting the accessKeyID and secretAccessKey from an already created Kubernetes Secret
-    auth:
-      secretRef:
-        accessKeyID:
-          name: awssm-secret
-          key: access-key
-
-        secretAccessKey:
-          name: awssm-secret
-          key: secret-access-key
-
-    # Role is a Role ARN which the SecretManager provider will assume
-    role: iam-role
-
-    # AWS Region to be used for the provider
-    region: eu-central-1
+  # provider field contains the configuration to access the provider which contains the secret
+  # exactly one provider must be configured. 
+  provider:
+    # AWSSM configures this store to sync secrets using AWS Secret Manager provider
+    awssm:
+      # Auth defines the information necessary to authenticate against AWS by 
+      # getting the accessKeyID and secretAccessKey from an already created Kubernetes Secret
+      auth:
+        secretRef:
+          accessKeyID:
+            name: awssm-secret
+            key: access-key
+
+          secretAccessKey:
+            name: awssm-secret
+            key: secret-access-key
+
+      # Role is a Role ARN which the SecretManager provider will assume
+      role: iam-role
+
+      # AWS Region to be used for the provider
+      region: eu-central-1
 
 status:
   # * Pending: e.g. referenced secret containing credentials is missing