Azure Pipeline

This setup is not supported by our pipeline action. It will build the zip file and create the function in the same codebase.

What’s the value of doing it with a single zip file? The contents of the zip file will the same when ran on the same source code.

Not sure I fully understand the question, but if you need to deploy to separate projects, I guess you can add multiple “Deploy Functions to CDF” steps in the pipeline, each pointing to different secrets/clientID/tenantID

We want to deploy the function in automated fashion in lower environment (e.g dev-CDF project , test CDF -project) from the single code base, and for deploying to production we want to manually execute release pipeline (based on our CR approvals and process). We will be tagging the master/main (version control) for  production deployment after we test in test CDF  project

We want to isolate CD(release) from CI(build) pipeline

I think you should be able to do that by having a different pipeline trigger, for example deploy to test with a "pull request trigger", test it and merge it to master after approval which would then deploy to production 

Hi @N G Nidhi @jaydeep just checking in to see if you could use more information from us with regards to the above, or if you’re all good for now? 

Hi @N G Nidhi, thanks so much for sharing with the community! 🙌