Question

CI/CD for Tracking Plan when the source is a CDP

  • 10 April 2024
  • 0 replies
  • 14 views

I love the way Amplitude deals with data governance! It makes so much sense to have a defined data tracking plan, and being able to make sure that all incoming events are a part of this plan.

In our team, we use 3 environments, translating to 3 Amplitude projects - Dev, Staging, and Prod.

I’d like to be able to “promote” a tracking plan from Dev to Staging to Prod. This would be achieved with the Ampli CLI, which seems like the right tool for the job.

My issue arise from my usage of a CDP (Rudderstack) between my code generating the events, and Amplitude.

The Ampli CLI ignores my Rudderstack source as it has no name - but I have no way to define a name for it in the UI.

 

I’d love to learn of different ways I can use the Amplitude Tracking Plan as part of my CI/CD pipeline, or how to use the Ampli CLI with a CDP source.

 

Thanks!

Irad


0 replies

Be the first to reply!

Reply