Event Stream Source Management using Rudder CLI Quickstart Alpha

This quickstart guide shows you how to use the Rudder CLI tool to create and deploy an Event Stream source to your workspace.

Prerequisites

• Rudder CLI tool (rudder-cli) installed locally
• An existing Tracking Plan defined in your CLI project (optional, but recommended for Data Governance)
• In your RudderStack workspace, create a workspace-level Service Access Token with the following permissions to manage Event Stream sources:

Click here to see how these permissions appear in the workspace policy.

Token permissions for legacy RBAC system

If you are on the legacy Permissions Management (RBAC) system, your workspace-level Service Access Token should have minimum Admin permissions.

See this documentation for more information on generating the token.

1. Authenticate the CLI tool

Run the following command and enter your access token when prompted:

rudder-cli auth login

2. Create a project directory

Create a project directory to store your source YAML files:

mkdir ~/tutorial-sources

If you are already managing Tracking Plans or Data Catalog resources via CLI, you can add source definitions to the same project directory. The CLI processes all YAML files in the directory recursively.

3. Review the YAML reference

Before defining your Event Stream source, review the Source YAML Reference to understand:

• The complete YAML structure for Event Stream sources
• Required and optional fields for source configuration
• Governance validation settings and violation rules
• Reference syntax for linking sources to Tracking Plans

Understanding the YAML reference will help you create properly structured files and avoid common validation errors when defining your sources.

4. Define an Event Stream source

Create a YAML file for your Event Stream source (~/tutorial-sources/ios-source.yaml):

version: rudder/v0.1
kind: event-stream-source
metadata:
  name: ios-source
spec:
  id: "my-ios-source"
  type: "ios"
  name: "iOS Source"
  enabled: true

This example creates a basic iOS source without governance configuration. The source accepts events and is enabled by default.

5. Optional: Add governance configuration

If you want to associate a Tracking Plan with your source for data governance, update the YAML file to include governance settings:

version: rudder/v0.1
kind: event-stream-source
metadata:
  name: ios-source
spec:
  id: "my-ios-source"
  type: "ios"
  name: "iOS Source"
  enabled: true
  governance:
    validations:
      tracking_plan: "#/tp/my-tracking-plan/my-tracking-plan"
      config:
        track:
          propagate_violations: true
          drop_unplanned_events: true
          drop_unplanned_properties: true
          drop_other_violations: true
        identify:
          propagate_violations: true
          drop_unplanned_properties: true
          drop_other_violations: true

In this example:

• The source is linked to a Tracking Plan referenced as #/tp/my-tracking-plan/my-tracking-plan.
• For track events, violations are propagated, unplanned events are dropped, unplanned properties are dropped, and other violations are dropped.
• For identify events, violations are propagated, unplanned properties are dropped, and other violations are dropped.

The Tracking Plan reference follows the format #/tp/[metadata.name]/[tracking-plan.id], where metadata.name is the metadata.name value in your Tracking Plan YAML file and tracking-plan.id is the spec.id value of the Tracking Plan.

See Source YAML Reference for detailed information about these configuration options.

6. Validate and deploy

1. Validate your files:

rudder-cli validate -l ~/tutorial-sources

2. Optional: Review changes before deploying:

rudder-cli apply -l ~/tutorial-sources --dry-run

3. Deploy changes to your workspace:

rudder-cli apply -l ~/tutorial-sources

Supported sources

You can define Event Stream source YAMLs only client-side and server-side SDK sources.

Rudder CLI does not support cloud apps and webhook sources currently.

Next steps

• See the Source YAML Reference for detailed YAML definitions of Event Stream source resources.
• See CLI-based Tracking Plan Management to create the Tracking Plans you reference in your source configurations.