Skip to content

Commit 6dd9655

Browse files
committed
remove vault-based credentials usage details for now
1 parent e894f75 commit 6dd9655

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

docs/credentials.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -151,20 +151,13 @@ Define the value as a reference to the corresponding key in the credentials file
151151
- `_CREDS` is an environment constant pointing to the `.credentials` file
152152
- `my_data_key` is a key in the the `.credentials` file or vault that contains the value to be used in a test step
153153
- for File Storage, ensure your key contains the vendor prefix, i.e. `vendor/my_data_key`
154-
- for Vault Storage, ensure your key contains your secret basepath + `/mftf/` + your vendor prefix + `/` and finally your key, i.e. `secret/mftf/vendor/my_data_key`
155154

156155
For example, to reference secret data in the [`fillField`][] action, use the `userInput` attribute using a typical File Storage:
157156

158157
```xml
159158
<fillField stepKey="FillApiToken" selector=".api-token" userInput="{{_CREDS.vendor/my_data_key}}" />
160159
```
161160

162-
To do the same using Vault Storage:
163-
164-
```xml
165-
<fillField stepKey="FillApiToken" selector=".api-token" userInput="{{_CREDS.secret/mftf/vendor/my_data_key}}" />
166-
```
167-
168161
<!-- {% endraw %} -->
169162

170163
## Implementation details

0 commit comments

Comments
 (0)