Transformations v2: General Availability

Transformations v2 is now Generally Available in all RudderStack plans. The testing suite and version controls from the public beta are the supported way to change transformation and library code before it reaches your destinations.

Why this matters

A transformation sits on the path of every event you send to a connected destination. A library change can affect every transformation that imports it. You can now validate those changes against real payloads, publish a tagged version when the tests pass, and deploy an earlier transformation version if a publish causes problems.

Key features

• Flexible testing: Import a live event or a saved payload, run it against your transformation, and compare Expected and Actual output in the Diff view. Approve a result to update the expected output, or Reject it to keep the current payload. Logs show output from your log() calls.
• Inferred library tests: Libraries don’t have their own test cases. Running a test on a library replays every test case from every transformation that imports it, so a breaking library change shows up before you publish.
• Drafts and tagged versions: Save draft stores work in progress without changing what destinations run. Publish creates a tagged version and makes it Active immediately for connected destinations. Version history records the code, tag, description, author, and timestamp.
• Validated rollback: Deploy an older transformation version back to Active. Test cases run against that version’s code first, so you can see whether the rollback is safe before you deploy. You can still deploy if tests fail.
• Library versions: Save drafts and publish tagged library versions the same way. Publishing a new version is how you change which library version is active. Transformations always import the Active published version, so publish a library before you import it.

Get started

1. Go to Collect > Transformations in the RudderStack dashboard and open or create a transformation.
2. In the Editor tab, write your code, create a test case, and click Run.
3. Click Save draft to keep changes out of production, or Publish to tag and activate a new version.
4. Open the Versions tab to review history or Deploy an older version back to Active.

See Test Transformations and Version and Deploy Transformations for the full workflow. Libraries use the same Editor and Versions tabs.

Resources

• Test Transformations: Create test cases, import event payloads, and use the diff view
• Version and Deploy Transformations: Save drafts, publish tagged versions, and roll back to an older version
• Version and publish libraries: Draft, publish, and view library version history
• Test a library: How library tests are inferred from importing transformations