eventstream-authoring-cli

Create and deploy Fabric Eventstream real-time streaming topologies via the Items REST API.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill eventstream-authoring-cli-9vantage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eventstream-authoring-cli
Source: https://github.com/9vantage/skills-for-fabric-clone/tree/main/plugins/fabric-authoring/skills/eventstream-authoring-cli
Command: npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill eventstream-authoring-cli-9vantage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Microsoft Fabric Eventstream pipelines requires assembling complex topology JSON with sources, operators, streams, and destinations, then base64-encoding and submitting it through the Items REST API. This Skill guides the AI through that entire authoring workflow, preventing common silent API rejections and misconfigurations. ## Core Features & Use Cases - Topology Authoring: Build Eventstream definitions with 25 source types (Event Hubs, IoT Hub, CDC, Kafka, SampleData), 8 operators (Filter, Aggregate, GroupBy, Join, ManageFields, Union, Expand, SQL), and 4 destinations (Lakehouse, Eventhouse, Activator, Custom Endpoint). - Full Lifecycle Management: Create, deploy, update, and delete Eventstreams via az rest calls, including base64 encoding of eventstream.json and LRO polling for definition updates. - Use Case: A data engineer needs a real-time ingestion pipeline that reads CDC events from a database, flattens Debezium payloads, filters records, and routes them to a Lakehouse. The Skill walks through building the topology JSON, encoding it, and deploying it in a single API call. ## Quick Start Ask the AI to create a Fabric Eventstream in your workspace with an Event Hubs source, a filter operator, and a Lakehouse destination using the eventstream authoring skill.

Frequently Asked Questions about eventstream-authoring-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Fabric Eventstream with the REST API?▼

Create an Eventstream by POSTing to the workspace eventstreams endpoint with a display name, then submit the topology via the definition API with base64-encoded eventstream.json. You can also deploy the full topology in one call using the Create Item with Definition endpoint.

How do I add a filter operator to an Eventstream topology?▼

Add a Filter node with inputNodes referencing the upstream stream and a conditions array in properties. Each condition must use nested objects: column with expressionType ColumnReference and value with expressionType Literal, since bare strings are silently rejected by the API.

What sources and destinations does Fabric Eventstream support?▼

The API supports 25 source types including Event Hubs, IoT Hub, CDC, Kafka, and SampleData, plus 4 destination types: Lakehouse, Eventhouse, Activator, and Custom Endpoint. Combined CustomEndpoint sources and destinations are limited to 11 per topology.

Why is my Eventstream definition update not applying?▼

The Update Definition API returns 202 Accepted as a long-running operation, so you must poll the Location header URL until completion. Also verify the payload is base64-encoded and that operator conditions use nested objects rather than bare strings.

What is the difference between Eventstream and Eventhouse in Fabric?▼

Eventstream is a real-time event ingestion and routing pipeline, while Eventhouse is a KQL database workload for storing and querying data. For KQL database operations, use the eventhouse-authoring-cli or eventhouse-consumption-cli skills instead.