[1ES Manage Images] base-images to 1es managed images

[AlitzelMendez]

move base-images to 1es managed images using bicep

Release Note Category

• [ ] Feature changes/additions
• [ ] Bug fixes
• [ ] Internal Infrastructure Improvements

  Release Note Description

[AlitzelMendez]

I started working on this and I created a draft pr with these changes: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines/pullrequest/34409

I am unassigning this issue to me as I will not continue working on this issue, but I want to provide a quick summary of what is going on around this, the main question is if we are going to use bicep of arm template Json.

the advantages that I see for bicep are:

• we can divide the definition of the resources into small bicep modules, which makes things a lot more organized, easy to read, understand and update as we can have a file per image
• there are tools that makes easier to write templates using bicep, such as bicep extension for vs code
• the bicep cli facilitates converting the bicep files to arm template Json if this is needed, so is not difficult to obtain the Json version
• it is what 1ES is promoting to use

the advantages that have been observed for arm template Json are:

• we know Json already, so there is not learning curve in this aspect
• the azure resources show the arm template Json view so is going to be easier to compare and we are going to be more familiar with it if we keep use arm templates

this is something that probably need more discussion so I just wanted to summarize the discussion so far and I am letting my draft in case is used and to give an example of bicep

[riarenas]

Thanks @AlitzelMendez, this is good groundwork. Even if we don't go with bicep, having them already written that way should even allow us to use the cli and just end up committing the json view instead.