Consider using YAML template io PowerShell to expose Bicep parameters

[stijnmoreels]

Currently, we publish a ./Deploy.ps1 PowerShell script that takes in all the Bicep parameters, does the deployment of all Bicep files and pushes all Container Apps in a single go. While this feels like a great and 'simple' way of exposing an Invictus deployment, it has some drawbacks:

No control over logging, validation failures, output.. which results in often tricky issue handling during ticket support.
High maintenance cost as all Azure CLI commands need to be kept up to date, while new functionality/approaches are often only lately discovered due to warnings that are almost always ignored by us during releasing.
High knowledge transfer/centralization, which makes the file both big and hard to change by others.

A possible alternative could be that we don't publish a PowerShell file but a YAML template which consumers can integrate in their CD pipeline. By doing so, we could make use of built-in Azure tasks that takes care of Bicep deployments, which immediately also includes better logging and validation failure reporting. It also allows consumers to manipulate the release to their choosing. Instead of a PowerShell script that manipulates Bicep parameter files from incoming PowerShell parameters, we could immediately accept a Bicep parameter file path in the YAML template, which allows easier control.

[stijnmoreels]

@GoutsmitSam , copied idea task from Azure DevOps to a discussion item here on GitHub + added a link to this discussion item in the idea task at Azure DevOps for traceability.