Introduce the automation of ARM template generation for ADF in the CI pipeline. Publish as build artifact. CD Pipeline then references these artifacts instead of the adf_publish branch.
Alternative Proposals
Since manual publish to adf_publish branch is still supported, should a new e2e sample be made to showcase the automation of publishing ADF artifacts?
Additional Context
My team is currently using the e2e parking sensor example as a starting point for our DataOps project. We are working to get the automation of ADF publish integrated into the CI/CD process. More than happy to contribute back to this repo once we get it working, but would like consensus on whether we should make a new directory under e2e_samples or replace what is already in the parking sensors sample. Since Microsoft documentation states that both manual and automated will be supported, would it make sense to have a sample showcasing each scenario?
Problem Statement
Proposed Solution
adf_publish
branch.Alternative Proposals
adf_publish
branch is still supported, should a new e2e sample be made to showcase the automation of publishing ADF artifacts?Additional Context
e2e_samples
or replace what is already in the parking sensors sample. Since Microsoft documentation states that both manual and automated will be supported, would it make sense to have a sample showcasing each scenario?Next Steps