$ loading_
通过 REST API 创建、更新并发布 Microsoft Fabric Eventstream 实时流拓扑。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "eventstream-authoring-cli" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/skills-for-fabric/main/skills/eventstream-authoring-cli/SKILL.md 2. 保存为 ~/.claude/skills/eventstream-authoring-cli/SKILL.md 3. 装好后重载技能，告诉我可以用了
请为 Microsoft Fabric 设计一个 Eventstream 拓扑：从 Azure Event Hubs 读取订单事件，先过滤无效记录，再按地区聚合销售额，最后分别写入 Lakehouse Delta 和 Eventhouse。请输出可发布的拓扑定义结构与关键配置说明。
一份可部署的 Eventstream 拓扑定义，包含源、算子、目标及连接关系说明。
帮我创建一个 Fabric Eventstream 定义：接入 SQL Server CDC 源，使用 SQL/Debezium 扁平化 payload，提取订单表和客户表变更，并将不同表的数据路由到各自的 DerivedStream。
包含 CDC 源配置、扁平化逻辑和多表分流路由的事件流定义方案。
请修改现有的 Fabric Eventstream：新增一个 Kafka 源，加入 Join 和 ManageFields 算子，将结果发送到 Custom Endpoint，并删除不再使用的旧目标。请给出更新后的拓扑定义。
更新后的 Eventstream 拓扑定义，明确新增、变更和删除的组件。
Update Check — ONCE PER SESSION (mandatory) The first time this skill is used in a session, run the check-updates skill before proceeding.
- GitHub Copilot CLI / VS Code: invoke the
check-updatesskill.- Claude Code / Cowork / Cursor / Windsurf / Codex: compare local vs remote package.json version.
- Skip if the check was already performed earlier in this session.
CRITICAL NOTES
- To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
- To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
- Eventstream ≠ Eventhouse. Eventstream is a real-time event ingestion and routing pipeline. For KQL database operations, use
eventhouse-authoring-clioreventhouse-consumption-cli.
| Task | Reference |
|---|
| Notes |
|---|
| Finding Workspaces and Items in Fabric | COMMON-CLI.md § Finding Workspaces and Items in Fabric | Mandatory — READ link first [needed for finding workspace id by its name or item id by its name, item type, and workspace id] |
| Fabric Topology & Key Concepts | COMMON-CORE.md § Fabric Topology & Key Concepts | |
| Environment URLs | COMMON-CORE.md § Environment URLs | |
| Authentication & Token Acquisition | COMMON-CORE.md § Authentication & Token Acquisition | Wrong audience = 401; read before any auth issue |
| Core Control-Plane REST APIs | COMMON-CORE.md § Core Control-Plane REST APIs | Includes pagination, LRO polling, and rate-limiting patterns |
| Gotchas, Best Practices & Troubleshooting | COMMON-CORE.md § Gotchas, Best Practices & Troubleshooting | |
| Tool Selection Rationale | COMMON-CLI.md § Tool Selection Rationale | |
| Authentication Recipes | COMMON-CLI.md § Authentication Recipes | az login flows and token acquisition |
Fabric Control-Plane API via az rest | COMMON-CLI.md § Fabric Control-Plane API via az rest | Always pass --resource; includes pagination and LRO helpers |
| Gotchas & Troubleshooting (CLI-Specific) | COMMON-CLI.md § Gotchas & Troubleshooting (CLI-Specific) | az rest audience, shell escaping, token expiry |
| Quick Reference | COMMON-CLI.md § Quick Reference | az rest template + token audience/tool matrix |
| Eventstream Resource Model | EVENTSTREAM-AUTHORING-CORE.md § Eventstream Resource Model | Read first — graph-based topology with sources, operators, streams, destinations |
| Source Configuration | EVENTSTREAM-AUTHORING-CORE.md § Source Configuration | 25 API-supported source types with per-source properties |
| Transformation Operators | EVENTSTREAM-AUTHORING-CORE.md § Transformation Operators | 8 operator types: Filter, Aggregate, GroupBy, Join, ManageFields, Union, Expand, SQL |
| Destination Configuration | EVENTSTREAM-AUTHORING-CORE.md § Destination Configuration | 4 API-supported destination types with node schema |
…