cloud live deploy: no Interactive Brokers (FIX) brokerage, --ib-fix-account / --ib-fix-user-name do not exist
维护者通常 6 天内回复
评估
调研方向
Start with lean/models/click_options.py:24-25 and lean/models/cloud/__init__.py:21-33 to see how cloud brokerage options are generated from modules-1.14.json, then read lean/models/json_module.py (get_user_name(), the Auth0 flow) and lean/components/util/auth0_helper.py. The JSON file lives on the CDN, so part of the change is outside this repo and needs maintainer coordination. Done means --brokerage "Interactive Brokers (FIX)" resolves, the --ib-fix-* options appear in lean cloud live deploy --help, and the Auth0 brokerage name and ib-fix-linked-account are sent correctly.
由索引模型根据 Issue 内容生成。
描述
lean cloud live deploy cannot create an Interactive Brokers (FIX) deployment. The cloud brokerage list the CLI builds from modules-1.14.json has one Interactive Brokers entry, InteractiveBrokersBrokerage (the IB Gateway integration: ib-user-name, ib-account, ib-password, ib-host, ib-port, ...). There is no InteractiveBrokersFixBrokerage module and no ib-fix-* option, in interactive or non-interactive mode, so a member who moved an IB account to the FIX integration (the route the Interactive Brokers docs now recommend for live accounts) can only deploy through the web wizard and loses scripted deployments.
The API side already supports it: /live/create accepts the InteractiveBrokersFixBrokerage module with ib-fix-account, ib-fix-user-name and ib-fix-linked-account (the IB user name whose Client Portal authorization the wizard stored), and live/auth0/read answers brokerage=InteractiveBrokersFixBrokerage with userId=<IB user name> by returning the linked accounts for that user name. The gap is in the CLI.
Reproduce
Lean CLI 1.0.233 (master fba6da7, 2026-10-27), modules-1.14.json fetched from https://cdn.quantconnect.com/cli/modules-1.14.json on 2026-10-31.
$ lean cloud live deploy "My Project" --brokerage "Interactive Brokers (FIX)" --ib-fix-account U1234567 --ib-fix-user-name someuser --node L-MICRO --auto-restart no --notify-order-events no --notify-insights no
Error: No such option '--ib-fix-account'. (Did you mean one of: '--eze-trading-account', '--ib-account', '--terminal-link-emsx-account'?)
$ lean cloud live deploy "My Project" --brokerage "Interactive Brokers (FIX)" --node L-MICRO --auto-restart no --notify-order-events no --notify-insights no
Error: Invalid value for '--brokerage': 'Interactive Brokers (FIX)' is not one of 'Paper Trading', 'Interactive Brokers', 'Tradier', 'Oanda', 'Bitfinex', 'Coinbase Advanced Trade', 'Binance', 'Zerodha', 'Samco', 'Terminal Link', 'Trading Technologies', 'Kraken', 'CharlesSchwab', 'Bybit', 'TradeStation', 'Alpaca', 'Tastytrade', 'Eze', 'dYdX', 'Webull', 'Public', 'ClearStreet'.
$ lean cloud live deploy --help | grep -- --ib-
--ib-user-name TEXT Your Interactive Brokers username
--ib-account TEXT Your Interactive Brokers account id
--ib-password TEXT Your Interactive Brokers password
--ib-host TEXT External Interactive Brokers Gateway Host
--ib-port TEXT External Interactive Brokers Gateway Port
--ib-weekly-restart-utc-time TEXT
--ib-financial-advisors-group-filter TEXT
InteractiveBrokersFixBrokerage as the --brokerage value fails the same way, and the interactive wizard offers the same 22 names.
Where
lean/models/__init__.py:20-26downloadsmodules-1.14.json;lean/models/cloud/__init__.py:21-33keeps the entries whoseplatformcontainscloudand whosetypecontainsbrokerageascloud_brokerages. The file has no FIX entry, solean/models/click_options.py:24-25never generates the options andlean/commands/cloud/live/deploy.py:290(non_interactive_config_build_for_name) cannot resolve the name.- The CLI already has the pattern a FIX entry needs: an
oauth-tokenconfiguration (lean/models/configuration.py:434-448,AuthConfiguration) withrequire-user-name: true, asCharlesSchwabBrokerageuses (charles-schwab-oauth-token+ acharles-schwab-account-numberchoice filtered on it).JsonModule.get_user_name()(lean/models/json_module.py:178-204) reads<prefix>-user-namefrom the options, and the Auth0 flow (json_module.py:311-330,lean/components/util/auth0_helper.py:19-44) callslive/auth0/readwithuserIdand offersaccountsfrom the response as the account choice.
Proposed change
- Add an
InteractiveBrokersFixBrokerageentry to the modules JSON (display idInteractive Brokers (FIX),platform: ["cloud"],type: ["brokerage"], minimum seat as the Gateway entry) with:ib-fix-oauth-token:type: oauth-token,require-user-name: true(so--ib-fix-user-nameis the IB user name the CLI authorizes with, matchingget_user_name()'s<prefix>-user-nameconvention);ib-fix-account:input-method: choice, filtered on the token, populated from theaccountsthe Auth0 read returns;- the settings sent to
/live/createmust includeib-fix-linked-accountset to the same IB user name (the factory requires it), so either the module maps it from the user name or the CLI adds it inget_settings()for this module.
- The Auth0 brokerage name the CLI sends is the lowercased display name (
json_module.py:318:self._display_name.lower()), which for the new entry would beinteractive brokers (fix);live/auth0/authorizeexpectsinteractivebrokersandlive/auth0/readacceptsinteractivebrokersfixbrokerage/interactivebrokersbrokerage. The CLI needs to send the module id (or an explicitauth0-brokeragefield from the JSON) rather than the display name, or the API needs the alias. - Document the new options on the
lean cloud live deploypage (today it lists the Gateway options only).
Untested: no diff, since the change spans the CDN modules file and the CLI.
Open questions
- Should
--ib-fix-user-namereuse the Gateway-style free text, or should the CLI require the user name to already be linked (the wizard's "+ Add Account" flow opens the IB login; the CLI'sauthorizeURL does the same withuserId)? - The paper-account rule (FIX does not support
DUaccounts) belongs in the module's validation.
Intercom conversation 215476644846297.
- 主要语言
- Python
- 星标
- 329
- 派生
- 169
- 平均合并
- 4 天 18 小时
- 30 天内合并 PR
- 9
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
QuantConnect/lean-cli 的其他 Issue
-
lean live deploy skips the localhost host rewrite and symbol map mount for brokerage settings可能已有人在做 @pcbeingused333 于 2 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 68/100
QuantConnect/lean-cli#690 ·
维护者通常 6 天内回复
-
cloud pull --encrypt leaves the project without its key path and encrypts referenced libraries可能已有人在做 @Amadeus-22 于 3 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 25/100
QuantConnect/lean-cli#688 ·
维护者通常 6 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
QuantConnect/lean-cli#681 ·
维护者通常 6 天内回复
-
lean cloud push overwrites read-only shared library files可能已有人在做 @Amadeus-22 于 3 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 55/100
QuantConnect/lean-cli#661 · 2 条评论 ·
维护者通常 6 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
QuantConnect/lean-cli#619 ·
维护者通常 6 天内回复
查看 QuantConnect/lean-cli 的全部 Issue
相似的 Issue
-
area:scripts area:tests bug priority:later
难度 2/5 1-3 小时 新手友好度 72/100
Ikalus1988/MisakaNet#4358 ·
维护者通常 1 天内回复
-
Discovered ports from service discovery are never propagated to modules in Module.load()可能已有人在做 @vishalmore90 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
OWASP/Nettacker#1828 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
aws-samples/sample-per-model-bedrock#708 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 75/100
sjkim1127/Reversecore_MCP#365 ·
维护者通常 1 天内回复