lark-cli 中转服务信息缺失
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.3k
- Forks
- 1.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 105
Description
对Lark CLI对应的自建应用设置IP白名单后，并已经将本机公网IP加入。仍出现如下报错：
错误码：99991401 错误信息：ip 54.166.211.53 is denied by app setting
错误码：99991401 错误信息：ip 3.211.55.69 is denied by app setting
从 IP 段来看（54.166.x.x、3.211.x.x），这两个地址属于 AWS EC2 的 IP 段。这说明 lark-cli 的 API 调用和 OAuth 授权流程并非直连飞书服务器，而是走了 AWS 托管的中转服务。
我想确认，lark-cli会通过其他服务中转后再去访问Lark的OpenAPI么？这个中转服务是什么？有文档说明么？具体的IP列表可否告知？
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or test. Trace the Lark CLI API request and OAuth authorization paths, then inspect the project’s deployment or documentation for any relay service and its egress IPs. Done means confirming whether AWS-hosted intermediary traffic is used and documenting the service and IP-list guidance needed to configure the app whitelist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100