docs(skill): clarify publishable-key guidance for CloudBase Web auth#475
docs(skill): clarify publishable-key guidance for CloudBase Web auth#475
Conversation
Resolves #469. Removed unsupported publishable-key API guidance (`DescribeApiKeyTokens`, `CreateApiKeyToken`) from `auth-tool`. Updated `auth-web` prerequisites so they no longer claim the key can be auto-fetched through MCP. Instructed agents to keep the auth UI visible and request/configure the publishable key manually from the console instead of failing or hiding the UI.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a86691830d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } | ||
| ``` | ||
| Return `PublishableKey.ApiKey` if exists (filter by `Name == "publish_key"`). | ||
| The CloudBase Web SDK requires a publishable key (`publishableKey`) during initialization when interacting with auth and other public APIs. |
There was a problem hiding this comment.
accessKey terminology for SDK init key
This sentence introduces publishableKey as if it were the Web SDK init field, which can lead agents to generate cloudbase.init({ publishableKey: ... }) and break auth initialization because the documented init option in the rest of this repo is accessKey (the publishable key value). Please reword this to avoid implying a new option name, e.g. “publishable key used as accessKey”.
Useful? React with 👍 / 👎.
1 participant
Summary
DescribeApiKeyTokens,CreateApiKeyToken) fromauth-tool.auth-webprerequisites so they no longer claim the key can be auto-fetched through MCP.Resolves #469.
Test plan