Alexander Sehr

While I think this could be enabled at any time - I wonder if it is still relevant once the new dependency approach #1791 is merged for all modules. There,...

> If yes, then maybe we can roll this out? Currently, there would not be a use case for the dependency pipeline to be supported in the future.

Hey @itpropro, even though I'd support the motion, a quorum decided to leave it as is for because a mix of quoted and unquoted strings in the list appears to...

Attached a Draft PR for reference

Hey @itpropro, I'll take care of it once #1898 is in to make it as easy for me as possible resolving conflicts. Should happen in the next couple days.

Merged and retesting

Will be introduced once the work surrounding #1624 is completed

Note, difference approaches. E.g. - Azure DevOps Pipeline Orchestration using the Mulit-Repository approach - Azure DevOps Pipeline Orchestration using the Azure DevOps Artifacts

I was fixed in that the variable is now used. However, the solution isn't ideal as @khaliddermoumi correctly pointed out it should reference `${name_var}` in the diagnostic settings name. The...

I guess it will come down to adding another service connection and referencing it in the publishing. Good idea