eventstream-authoring-cli

Create and update Microsoft Fabric Eventstream definitions from graph-based configurations.

3|6|Updated Jun 21, 2024

Search Tags:#streaming #rest api #topology #cdc #eventstream #microsoft fabric #real-time analytics

Ready to run

npx skills add https://github.com/rritec/Microsoft-Fabric --skill eventstream-authoring-cli-rritec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eventstream-authoring-cli
Source: https://github.com/rritec/Microsoft-Fabric/tree/main/skills/plugins/fabric-authoring/skills/eventstream-authoring-cli
Command: npx skills add https://github.com/rritec/Microsoft-Fabric --skill eventstream-authoring-cli-rritec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of creating, updating, and deploying Microsoft Fabric Eventstream topologies so you can build real-time ingestion flows without manually stitching together REST payloads and stream routing logic.

Core Features & Use Cases

Topology authoring: Create graph-based Eventstream definitions with sources, streams, operators, and destinations.
Real-time routing: Support fan-out pipelines, derived streams, and destination targets such as Lakehouse Delta, Eventhouse, Activator, and custom endpoints.
Lifecycle management: Create, update, and delete Eventstream items through the Fabric control-plane APIs with the right encoding and polling patterns.
Use case: A data team can model an IoT or CDC pipeline, flatten incoming events, route them to multiple destinations, and publish the complete topology in one controlled workflow.

Quick Start

Ask the skill to create or update a Microsoft Fabric Eventstream topology for your workspace and deploy it through the Fabric Items REST API.

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 Microsoft Fabric Eventstream topology via REST API?▼

Create a Fabric Eventstream topology by submitting base64-encoded graph configurations to the Fabric Items REST API, then poll LRO endpoints for deployment completion.

Can I route real-time CDC events to multiple destinations in a Fabric Eventstream?▼

Yes, Eventstream topology authoring supports fan-out routing of CDC events to multiple destinations including Lakehouse, Eventhouse, Activator, and custom endpoints within a single definition.

What sources are supported for real-time ingestion pipelines in Microsoft Fabric Eventstreams?▼

Supported real-time ingestion sources for Fabric Eventstreams include Event Hubs, IoT Hub, Kafka, CDC connectors, and SampleData for stream processing and destination routing.

How do I update an existing Eventstream definition without recreating the item?▼

Update existing Eventstream definitions by modifying graph-based source, operator, and destination configurations, then applying the new base64-encoded payload through the Fabric control-plane REST API.

Does deploying an Eventstream require JMESPath filtering?▼

Yes, deploying an Eventstream uses JMESPath filtering to query workspace and item identifiers from API responses before submitting base64-encoded topology payloads for REST deployment.

Why does my Eventstream deployment fail when using the Fabric REST API?▼

Eventstream REST API deployment fails if topology payloads are incorrectly base64-encoded, if JMESPath workspace discovery is inaccurate, or if LRO polling is not implemented to confirm deployment completion.