|
|
@@ -51,12 +51,12 @@ See here for a list of [publicly available endpoints](https://cloud.ibm.com/apid
|
|
|
### Secret Types
|
|
|
We support the following secret types of [IBM Secrets Manager](https://cloud.ibm.com/apidocs/secrets-manager):
|
|
|
|
|
|
-* `arbitrary`,
|
|
|
-* `username_password`,
|
|
|
+* `arbitrary`
|
|
|
+* `username_password`
|
|
|
* `iam_credentials`
|
|
|
* `imported_cert`
|
|
|
* `public_cert`
|
|
|
-* and `kv`.
|
|
|
+* `kv`
|
|
|
|
|
|
To define the type of secret you would like to sync you need to prefix the secret id with the desired type. If the secret type is not specified it is defaulted to `arbitrary`:
|
|
|
|
|
|
@@ -85,7 +85,7 @@ The behavior for the different secret types is as following:
|
|
|
* `dataFrom` retrieves all `certificate`, `private_key` and `intermediate` fields from the secrets manager secret and sets appropriate key:value pairs in the resulting Kubernetes secret
|
|
|
|
|
|
#### kv
|
|
|
-* `remoteRef` could has a `property` to select requested key from the KV secret, otherwise the entire secret will be returned
|
|
|
+* An optional `property` field can be set to `remoteRef` to select requested key from the KV secret. If not set, the entire secret will be returned
|
|
|
* `dataFrom` retrieves a string from secrets manager and tries to parse it as JSON object setting the key:values pairs in resulting Kubernetes secret if successful
|
|
|
|
|
|
```json
|
Hafid.Haddouti