Before this PR, ADO pipelines created by MLOps Stacks for one repo in an ADO project would be run on pull requests against all other repos in the same ADO project. This PR isolates the ADO branch policies on a repo level. It also augments the names of provisioned things with the repo name for clarity.
Testing
I created two MLOps Stack projects based off of this feature branch and ran through the bootstrap scripts for both of them as two repos in the same ADO project. This resulted in the following ADO pipelines:
Then, I created one ML code PR and one Databricks Config PR for one of the repos. See below that only the ADO pipelines for that repo were triggered:
Description
Before this PR, ADO pipelines created by MLOps Stacks for one repo in an ADO project would be run on pull requests against all other repos in the same ADO project. This PR isolates the ADO branch policies on a repo level. It also augments the names of provisioned things with the repo name for clarity.
Testing
I created two MLOps Stack projects based off of this feature branch and ran through the bootstrap scripts for both of them as two repos in the same ADO project. This resulted in the following ADO pipelines:
Then, I created one ML code PR and one Databricks Config PR for one of the repos. See below that only the ADO pipelines for that repo were triggered: