Creating markdown table for workbook - Bicep escaping

[jordylangermans]

Hello,

I'm trying to create a dynamic markdown table for an Azure workbook. Because of some loop limitiations and the that the data is stored, I make use of powershell to create a string and pass the string as parameter to the bicep file.

The powershell created the string:

| Name | Protocols | Source adresses | Destination Addresses | Destination FQDNS | Destination Ports | \n| ------------- | ------------- | ------------- | ------------- | ------------- | ------------- | \n|Name1|TCP|0.0.0.0|0.0.0.0||8001| \n

Bicep code:
param workbookFirewallString string

var workbookFirewallRules = [for rule in firewallRulesJson: {
type: 1
content: {
json: workbookFirewallString this is the string from powershell
}
name: rule.name
}]

var workbookContent = {
version: 'Notebook/1.0'
items: [
{
type: 12
content: {
version: 'NotebookGroup/1.0'
groupType: 'editable'
title: 'Firewall rules'
items: workbookFirewallRules
}
name: 'workbookFirewallRules.name'
}
]
isLocked: false
fallbackResourceIds: [
law.id
]
}

The expected string that Azure needs is the same as the created powershell string.

But after the deployment bicep, arm or azure is escaping the \n to \ \n (without white space)

The \n represents a enter after every row for the markdown table.

[brwilkinson]

does the following work

var test = '''
 I am a string
 on a multiline
'''

[brwilkinson]

What if you just write, then read the file with loadTextContent() ?

[jordylangermans]

It's not possible to use Bicep for the processing, as mentioned before this has to do with the way the textfiles are written. There is a need to do 4 loops. I know it is possible with creating modules, but then I got 5 module files for 1 functionality. Powershell can do this job much easier. But this is another problem, I think this has nothing to do with the question. The problem is that Bicep is escaping the /n string.

What do you mean with just write?

[brwilkinson]

You can still write the file with powershell, however instead of passing it in via a parameter, just read it directly from the file with loadTextContent().

[jordylangermans]

I got you, but the problem is not passing the string as parameter from powershell to bicep. The problem starts when bicep deployment take place. After the deployment Bicep, ARM or Azure is escaping the \n to \ \n (without space)

If it is possible to make the multiline string with an dynamic index, I would like to know how.

[brwilkinson]

Try it out, I think it should solve your issue. Don't place any special characters in the markdown file, just keep it as a raw MD file, then read it with loadTextContent.

Write it to an output variable then share the result here. From the output.

[jordylangermans]

Creating markdown table for workbook - Bicep escaping #8573