eventstream-authoring-cli

Name: eventstream-authoring-cli
Availability: InStock
Author: weiflycc-cmd

Automate Microsoft Fabric Eventstream topology creation, modification, and deployment via REST API.

Updated Jun 1, 2026

Search Tags:#data pipeline #rest api #cli automation #eventstream #microsoft fabric #real-time ingestion #event topology

Ready to run

npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill eventstream-authoring-cli-weiflycc-cmd

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of building, configuring, and deploying Microsoft Fabric Eventstream real-time event streaming topologies, removing the need to handle low-level REST API calls, base64 encoding, and complex topology JSON structuring manually.

Core Features & Use Cases

Full Eventstream Lifecycle Management: Create, update, and delete Eventstream items and their topologies via the Fabric Control Plane REST API.
Graph-Based Topology Building: Supports 25 source types (Event Hubs, IoT Hub, CDC connectors, Kafka, SampleData), 8 transformation operators (Filter, Aggregate, GroupBy, Join, ManageFields, Union, Expand, SQL), and 4 destination types (Lakehouse Delta, Eventhouse, Activator, Custom Endpoint), with DefaultStream and DerivedStream routing.
Use Case Example: Deploy a CDC source that flattens Debezium payloads and routes processed data to multiple downstream destinations in a single workflow.

Quick Start

Use the eventstream-authoring-cli skill to deploy a complete Eventstream topology that ingests Kafka event data, applies filter and aggregate transformations, and routes the results to an Eventhouse destination.

Frequently Asked Questions about eventstream-authoring-cli

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

FAQPage Schema

How do I automate Microsoft Fabric Eventstream deployment via CLI?▼

You can automate Microsoft Fabric Eventstream deployment by using the Fabric Control Plane REST API to create, modify, and deploy real-time event streaming topologies programmatically. This handles base64 encoding, workspace discovery, and long-running operation polling automatically.

What types of real-time data sources and transformations does Fabric Eventstream support?▼

Fabric Eventstream supports 25 source types including Event Hubs, IoT Hub, Kafka, and CDC connectors. It provides 8 transformation operators like Filter, Aggregate, GroupBy, Join, and SQL, enabling complex graph-based event pipeline design for real-time data processing.

Can I route processed event data to multiple destinations in a single Eventstream topology?▼

Yes, Eventstream supports routing processed data to multiple downstream destinations using DefaultStream and DerivedStream routing. You can direct your real-time event data to Lakehouse Delta, Eventhouse, Activator, or Custom Endpoints within a single workflow.

What is the best way to flatten Debezium CDC payloads in an Eventstream pipeline?▼

The best way to flatten Debezium CDC payloads is to deploy a Change Data Capture source and apply transformation operators within your Eventstream topology. This automates payload flattening and routes the processed data to downstream destinations.

How does CLI automation handle long-running Eventstream lifecycle operations?▼

CLI automation manages long-running Eventstream lifecycle operations by polling the Fabric Control Plane REST API. It handles item ID discovery via JMESPath filtering and base64 encoding of definition payloads to ensure reliable event topology management.

Do I need to manually encode Eventstream topology JSON when using REST API automation?▼

No, you do not need to manually encode topology JSON or handle low-level REST API calls. Eventstream automation handles base64 encoding of definition payloads and complex topology JSON structuring, eliminating manual error-prone configuration work.