@@ -18,7 +18,7 @@ name: my-credential-tool
18
18
19
19
# !/usr/bin/env bash
20
20
21
- output=$(gptscript -q --cache=false sys.prompt '{"message":"Please enter your fake credential.","fields":"credential","sensitive":"true"}')
21
+ output=$(gptscript -q --disable- cache sys.prompt '{"message":"Please enter your fake credential.","fields":"credential","sensitive":"true"}')
22
22
credential=$(echo $output | jq -r '.credential')
23
23
echo "{\"env\":{\"MY_ENV_VAR\":\"$credential\"}}"
24
24
```
@@ -57,10 +57,12 @@ This config file also has another parameter, `credsStore`, which indicates where
57
57
58
58
- ` file ` (default): The credentials are stored directly in the config file.
59
59
- ` osxkeychain ` : The credentials are stored in the macOS Keychain.
60
+ - ` wincred ` : The credentials are stored in the Windows Credential Manager.
60
61
61
- In order to use ` osxkeychain ` as the credsStore, you must have the ` gptscript-credential-osxkeychain ` executable
62
- available in your PATH. There will probably be better packaging for this in the future, but for now, you can build it
63
- from the [ repo] ( https://github.com/gptscript-ai/gptscript-credential-helpers ) .
62
+ In order to use ` osxkeychain ` or ` wincred ` as the credsStore, you must have the ` gptscript-credential-* ` executable
63
+ available in your PATH. There will probably be better packaging for this in the future, but for now, you can build them
64
+ from the [ repo] ( https://github.com/gptscript-ai/gptscript-credential-helpers ) . (For wincred, make sure the executable
65
+ is called ` gptscript-credential-wincred.exe ` .)
64
66
65
67
There will likely be support added for other credential stores in the future.
66
68
0 commit comments