Bicep ProgramSyntax / SyntaxTree feature

[kilasuit]

To be more able to statistically analyse Bicep files, or programmatically build them, there should be a mechanism to convert a bicep file into usable Objects within PowerShell

[StefanIvemo]

Build-Bicep have a -AsHashtable switch. Is this what you are looking for?

[SimonWahlin]

We've been entertaining the idea of returning some kind of BicepTemplate object similar to Bicep.Core.Syntax.ProgramSyntax and similar to the PowerShell AST.

The problem is that since bicep has dependencies that are in conflict with other modules and PowerShell itself (Newtonsoft.Json), we are using the module BicepNet.PS to stand up an assembly load context where we can load all the bicep dlls in it's own "bubble". This means that we cannot expose the native types from bicep but will have to maintain our own classes representing the same types, which might end up being quite a lot of work.

We currently haven't found any scenarios where we feel the benefit of having this rich syntax tree motivates the effort to maintain it. However if you have any specific scenarios I'm open for a discussion.

[kilasuit]

@StefanIvemo - that may do thou let me play a bit more

@SimonWahlin please see this kilasuit/ARMTemplateComplexity#11 as to why I would like to have a proper bicepfile type similar to those that I have built in that repo for ARM templates and other json files.

I think it's perhaps worth me trying to get some time with @alex-frankel to discuss further too prior to the bicep community call this month if I can