Dynamic Pipelines Provider Best Practices?

[plussier]

Hi all,

The more I dive into dynamic pipelines the more interested and excited I am about them.  As my brain spins I'm starting to think we probably want more than just a single provider, possibly different providers to handle different code bases or something.  

We have many repositories ranging from Java code using both Maven & Gradle, NodeJS, Python, bash, Terraform, mixed repos with Java + Terraform, etc. This leads to thinking we maybe want to have multiple repos for our dynamic pipeline provider code; a base repo that's shared across all providers, then the provider specific code that would import the core repo.  Each of these repos of course would also have a full suite of unit tests (Jest?) as well, and ideally, hooked into auto deployment to Forge and promotion across dev/stage/prod with integration testing as well.

Does this line of thinking make sense?

I'm entirely new to TypeScript/NodeJS (not that I think that matters much) and dynamic pipeline/Forge development. Therefore I'm wondering what other heavy users of dynamic pipelines do, how you structure your code base for this stuff, etc.

Any advice or direction greatly appreciated.

Thanks.

--

Paul