Manage Transformations Using Rudder CLI

You can leverage Rudder CLI to manage Transformations and Transformation Libraries as code using a YAML-driven workflow. You can keep transformation code and test definitions in your repository, validate changes locally, and apply updates to your workspace in a controlled way.

Key features

With Rudder CLI’s transformations management feature, you get the following capabilities:

Declarative YAML configuration

• Define both transformation and transformation-library resources in YAML files
• Write transformation code inline or reference external code files
• Include local test suites alongside your transformation definitions
• Validate configurations locally before deployment

Local testing and safer deployment workflow

• Test individual, all, or only modified transformations
• Compare actual output against expected results
• Preview changes with a dry run before applying them to your workspace

Git integration and CI/CD support

• Keep transformation specs, code, and test fixtures version-controlled in Git
• Reuse the same commands locally and in CI pipelines
• Use a review-first Validate > Test > Apply workflow

Who can use this feature?

The CLI-based transformations workflow is useful to:

• Manage transformations and libraries programmatically with consistent standards
• Test transformation behavior before publishing updates
• Keep transformation code and tests in the same repository and review process
• Automate validation and deployment in CI/CD

Get started

• See the End-to-End Walkthrough: Transformations Management with Rudder CLI to create, validate, test, and apply transformations using Rudder CLI
• See the Transformations YAML Reference for complete YAML schemas, constraints, and examples
• Link a transformation to a destination in the Destination YAML Reference
• Automate with GitHub Actions
• Automate with GitLab CI/CD