Support bearerToken for BYO-K
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
### Describe the feature or problem you'd like to solve
In corp context, key based auth is disabled per compliance requirements. BearedToken based auth or customized broker would be helpful to automate the CLI runs.
### Proposed solution
Similar as what have been offered in GitHub Copilot SDK.
https://docs.github.com/en/copilot/how-tos/copilot-sdk/auth/byok#providerconfig-fields
field| type| description
-- | -- | --
bearerToken / bearer_token | string | Bearer token auth (takes precedence over apiKey)
bearerTokenProvider / bearer_token_provider | callback | Returns a bearer token on demand (takes precedence over apiKey and bearerToken)
### Example prompts or workflows
_No response_
### Additional context
_No response_
贡献指南
调研方向
先阅读现有的 CLI BYO-K 配置和 apiKey 身份验证流程,然后将其与所链接的 GitHub Copilot SDK provider 字段进行比较。当 CLI 运行可以使用 bearerToken 或 bearerTokenProvider 进行身份验证,并且这些选项优先于 apiKey 时,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- shell
- 领域
- authentication, cli
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100