fix(openclaw): surface tenant headers in remote setup#1707
Open
Hinotoi-agent wants to merge 1 commit intovolcengine:mainfrom
Open
fix(openclaw): surface tenant headers in remote setup#1707Hinotoi-agent wants to merge 1 commit intovolcengine:mainfrom
Hinotoi-agent wants to merge 1 commit intovolcengine:mainfrom
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
accountIdanduserIdprompts to OpenClaw remote-mode setup so root-key users can configure the tenant headers required by tenant-scoped OpenViking APIs.accountId/userIdconfiguration in both English and Chinese install guides.Fixes #1700.
Why
OpenViking now requires ROOT/root-key requests to tenant-scoped APIs to include
X-OpenViking-AccountandX-OpenViking-User. The OpenClaw plugin client already supports these headers throughaccountIdanduserId, but the supported setup/docs path only exposedbaseUrl,apiKey, andagentId. A user following the documented remote-mode setup withroot_api_keycan therefore hit the reportedINVALID_ARGUMENTerror after upgrade.Affected files
examples/openclaw-plugin/commands/setup.tsexamples/openclaw-plugin/setup-helper/install.jsexamples/openclaw-plugin/INSTALL.mdexamples/openclaw-plugin/INSTALL-ZH.mdexamples/openclaw-plugin/tests/ut/setup-command.test.tsTest plan
node --check examples/openclaw-plugin/setup-helper/install.jsnpm test -- --run tests/ut/setup-command.test.ts tests/ut/client.test.tsfromexamples/openclaw-pluginnpm test -- --run tests/ut/setup-command.test.tsfromexamples/openclaw-plugingit diff --checkNote: I also tried
tests/ut/config.test.ts, but currentmainappears to have stale assertions expecting the default mode to belocalwhileconfig.tsnow defaults invalid/missing mode toremote; that failure is unrelated to this patch.