@@ -230,7 +230,12 @@ Any valid secret name.
230230<tr >
231231<td ><code >fieldName</code ></td >
232232<td >
233- Optional key to extract a specific field from a JSON-formatted secret.
233+ The field inside the secret that contains the username.
234+ Use this parameter only when the secret is stored as a key-value pairs.
235+ If the secret contains multiple keys, this parameter specifies which key to extract.
236+ If the secret contains only one key and this parameter is not provided, that value is automatically used.
237+ If <code >fieldName</code > is provided but does not match any key, or if the secret is not structured as key/value pairs, an error is thrown.
238+ If the secret is plain text and <code >fieldName</code > is provided, an error is also thrown.
234239<td >
235240Key name in JSON
236241</td >
@@ -275,8 +280,12 @@ Any valid secret name.
275280<tr >
276281<td ><code >fieldName</code ></td >
277282<td >
278- Optional key to extract a specific field from a JSON-formatted secret.
279- <td >
283+ The field inside the secret that contains the password.
284+ Use this parameter only when the secret is structured as key-value pairs.
285+ If the secret contains multiple keys, this parameter specifies which key to extract.
286+ If the secret contains only one key and this parameter is not provided, that value is used automatically.
287+ If <code >fieldName</code > is provided but does not match any key, or if the secret is not structured as key-value pairs, an error is thrown.
288+ If the secret is stored as plain text and <code >fieldName</code > is provided, an error is also thrown.<td >
280289Key name in JSON
281290</td >
282291<td >
@@ -329,17 +338,6 @@ Any valid secret name.
329338</td >
330339</tr >
331340<tr >
332- <td ><code >fieldName</code ></td >
333- <td >
334- Optional key to extract a specific field from a JSON-formatted secret.
335- <td >
336- Key name in JSON
337- </td >
338- <td >
339- <i >Optional</i >
340- </td >
341- </tr >
342- <tr >
343341<td ><code >walletPassword</code ></td >
344342<td >
345343Optional password for PKCS12 or protected PEM files. If omitted, the file is assumed to be SSO or an non-protected PEM file.
@@ -359,6 +357,21 @@ Specifies the type of the file being used.
359357<i >No default value. The file type must be specified.</i >
360358</td >
361359</tr >
360+ <tr >
361+ <td ><code >fieldName</code ></td >
362+ <td >
363+ The field inside the secret that contains the base64-encoded TCPS wallet.
364+ Use this parameter only when the secret is structured as key-value pairs.
365+ If the secret contains multiple keys, this parameter specifies which key to extract.
366+ If the secret contains only one key and this parameter is not provided, that value is used automatically.
367+ If <code >fieldName</code > is provided but does not match any key, or if the secret is not structured as key-value pairs, an error is thrown.
368+ If the secret is stored as plain text and <code >fieldName</code > is provided, an error is also thrown.<td >
369+ Key name in JSON
370+ </td >
371+ <td >
372+ <i >Optional</i >
373+ </td >
374+ </tr >
362375</tbody >
363376</table >
364377
@@ -430,8 +443,12 @@ Optional parameter to specify the index of the connection string to use when ret
430443<tr >
431444<td ><code >fieldName</code ></td >
432445<td >
433- Optional key to extract a specific field from a JSON-formatted secret.
434- <td >
446+ The field inside the secret that contains the base64-encoded SEPS wallet.
447+ Use this parameter only when the secret is structured as key-value pairs.
448+ If the secret contains multiple keys, this parameter specifies which key to extract.
449+ If the secret contains only one key and this parameter is not provided, that value is used automatically.
450+ If <code >fieldName</code > is provided but does not match any key, or if the secret is not structured as key-value pairs, an error is thrown.
451+ If the secret is stored as plain text and <code >fieldName</code > is provided, an error is also thrown.<td >
435452Key name in JSON
436453</td >
437454<td >
@@ -453,11 +470,15 @@ This provider retrieves and decodes a `tnsnames.ora` file stored as a secret in
453470
454471You can store the contents of the tnsnames.ora file either as:
455472
456- - A base64-encoded string, or
473+ - A base64-encoded string, either directly or within a key inside a structured key-value map.
474+
475+ - Plain text, by simply copying and pasting the contents directly into the secret value.
457476
458- - Plain text, by simply copying and pasting the contents directly into the secret value field.
477+ If the secret is a key-value map, the <code >fieldName</code > parameter must be used to specify the key that holds the base64-encoded
478+ tnsnames.ora content.
459479
460- The provider will automatically handle either format and extract the appropriate connection string based on the specified alias.
480+ If the secret is stored as plain text, it must be provided as the raw contents of the tnsnames.ora file,
481+ and <code >fieldName</code > should not be set.
461482
462483This enables flexible configuration for secure database connections using the alias names defined in your ` tnsnames.ora ` file.
463484
@@ -487,7 +508,15 @@ In addition to the set of [common parameters](#common-parameters-for-resource-pr
487508 </tr >
488509 <tr >
489510 <td><code>fieldName</code></td>
490- <td>Optional key to extract a specific field from a JSON-formatted secret.</td>
511+ <td>
512+ The field inside the secret that contains the base64-encoded <code>tnsnames.ora</code> content.
513+ Use this parameter only when the secret is structured as key-value pairs.
514+ If the secret contains multiple keys, this parameter specifies which key to extract.
515+ If the secret contains only one key and this parameter is not provided, that value is used automatically.
516+ If <code>fieldName</code> is provided but does not match any key, or if the secret is not structured
517+ as key-value pairs, an error is thrown. If the secret is stored as plain text and <code>fieldName</code> is provided,
518+ an error is also thrown.
519+ </td>
491520 <td>Key name in JSON</td>
492521 <td><i>Optional</i></td>
493522 </tr >
0 commit comments