Create ADO pipelines for validate, deploy, remove & publish

[AlexanderSehr]

Change

• Created Azure DevOps pipelines for validate, deploy, remove & publish

• Renamed GitHub variables file to global.variables.json to align with the Azure DevOps variable file (which has a better name - global.variables.yml)

• Overhauled documentation

  • Added Azure DevOps sections where appropriate
  • Fixed incorrect wiki content (e.g. outdated environment variables, links, etc.)
  • Restructured the location of information a bit

• Tested:

  • Repo in GitHub, executing in Azure DevOps
  • Analysis Services, vWAN & Virtual Machines
  • Azure DevOps Artifacts
  • Multi Repo approach

• Out of scope

  • Platform pipelines (e.g. readMe update). Those can be added in a later PR

Notes:

• Leverages Azure DevOps Library Group for the same secrets as GitHub (e.g. subscription Id)
• The Azure DevOps triggers that use wildcards do currently not work. This feature was rolled out, and then rolled back and is lacking any update ever since. The only alternative are 'full-file-paths' which is not really an alternative at all. I'd keep it as is until the feature starts working again

Pipeline reference

See IaCS Pipelines in folder 'CARML-Modules'

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update (Wiki)

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code

[MariusStorhaug]

I am in the progress of reviewing. Its just a big PR...

[MariusStorhaug]

Based on the file name change, should we not replace the following:

- variableFileName: 'variables.module'
+ variableFileName: 'global.variables'

[MariusStorhaug]

Need to have a look at how we allow the action to also work with ARM/json template files.

[MariusStorhaug]

What about child resources? They are not nested templates when converted to json. Should we also remove/clean up the folders representing the child resources?

[MariusStorhaug]

All of my comments are fixed. Approved.

Marius did just that ;)