Bicep - Inject Xml

[gverstraete]

We want to inject API-M policies, which are xml files.
But in the InjectARM, you can just write plain xml and it is the InjectARM script that turns this into encoded values so the bicep can handle it.

When you use https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-files you also do have this issue.

So basically I would like a bicep version of : https://github.com/arcus-azure/arcus.scripting/blob/main/src/Arcus.Scripting.ARM/Scripts/Inject-ArmContent.ps1

[stijnmoreels]

@gverstraete , something you want to investigate yourself?
@pim-simons , I remember something before that we had this talk about a Bicep variant, but that continue as it was not needed at the time. Is this about something else?

Thinking that we might also need a dedicated 'infra as code' module, instead of based on technology? Or would the .ARM module still be suitable for this as it is talking about 'Azure Resource Manager' and not about the actual 'infra as code file type'.

[pim-simons]

To be honest, I have personally never really used https://github.com/arcus-azure/arcus.scripting/blob/main/src/Arcus.Scripting.ARM/Scripts/Inject-ArmContent.ps1 so I don't have that much experience with it.

If I remember correctly we indeed has a discussion around a bicep version and we concluded that these functions would most probably cover all that is needed.

When you use learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-files you also do have this issue.

I don't completely understand what the issue is that we would solve with a bicep version of https://github.com/arcus-azure/arcus.scripting/blob/main/src/Arcus.Scripting.ARM/Scripts/Inject-ArmContent.ps1. But again that might be because of my limited experience with the ARM version.

[gverstraete]

The thing is dat these function do not escape the xml, which the inject does do.
We mostly use this for importing API's in API-M.
Thing is that it seems by now we are using more the azure cli for this task... (az apim import)

[pim-simons]

Thing is that it seems by now we are using more the azure cli for this task... (az apim import)

So that means a Bicep version of the ARM Inject is not necessary anymore due to us mostly using az apim import? Or do I misunderstand?

[gverstraete]

Thing is that it seems by now we are using more the azure cli for this task... (az apim import)

So that means a Bicep version of the ARM Inject is not necessary anymore due to us mostly using az apim import? Or do I misunderstand?

Well, I don't how others use it, but I think the cli is just a workaround, I think it still makes sense to do it in bicep. Or if you tell me that there is a bicep out of the box solution I didn't think about...