Commit 48dd824
committed
Fix auth token precedence: use resolveAPIKey() in getDefaultRequestOptions
getDefaultRequestOptions checked HYPEMAN_API_KEY and config api_key but
ignored HYPEMAN_BEARER_TOKEN, while resolveAPIKey gave HYPEMAN_BEARER_TOKEN
highest precedence. Commands like cp/exec that use both paths could
authenticate SDK calls and WebSocket calls with different tokens.
Delegate to resolveAPIKey() so both paths share the same precedence:
HYPEMAN_BEARER_TOKEN > HYPEMAN_API_KEY > config api_key.1 parent 8674492 commit 48dd824
1 file changed
+3
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
39 | 39 | | |
40 | 40 | | |
41 | 41 | | |
42 | | - | |
| 42 | + | |
43 | 43 | | |
44 | | - | |
| 44 | + | |
| 45 | + | |
45 | 46 | | |
46 | | - | |
47 | | - | |
48 | 47 | | |
49 | 48 | | |
50 | 49 | | |
| |||
0 commit comments