How to load multiple template parameter files in BICEP

To use multiple parameter files with loadTextContent in Bicep, you can create a parameter that uses loadTextContent() or other loadX() to read the file. By having this in the parameter file instead of the template, you get some degree of flexibility to read different files based on the parameter file you are using. Here’s an example of how you can modify your Bicep code to load multiple parameter files: param nsgs array = [] param allowedVNetPrefixes array = [] param logRetentionDays int = 0 param subscriptionId string = subscription().subscriptionId param nsgFlowLogFilePath string var nsgFlowLog = json(loadTextContent(nsgFlowLogFilePath)) var networkWatcherName = '${nsgFlowLog.networkWatcherName}' var location = '${nsgFlowLog.location}' var storageId = '${nsgFlowLog.storageId}' var nsgResourceGroupName = '${nsgFlowLog.nsgResourceGroupName}' var workspaceId = '${nsgFlowLog.workspaceId}' var workspaceRegion = '${nsgFlowLog.workspaceRegion}' var workspaceResourceId = '${nsgFlowLog.workspaceResourceId}' resource flowLog 'Microsoft.Network/networkWatchers/flowLogs@2022-01-01' = [for nsg in nsgs: { name: '${networkWatcherName}/Microsoft.Network${nsgResourceGroupName}NSG_${replace(nsg.subnet, '/', '_')}' location: location properties: { targetResourceId: '/subscriptions/${subscriptionId}/resourceGroups/${nsgResourceGroupName}/providers/Microsoft.Network/networkSecurityGroups/NSG_${replace(nsg.subnet, '/', '_')}' storageId: storageId enabled: true format: { type: 'JSON' version: 2 } retentionPolicy: { days: logRetentionDays enabled: true } flowAnalyticsConfiguration: { networkWatcherFlowAnalyticsConfiguration: { enabled: true workspaceId: workspaceId workspaceRegion: workspaceRegion workspaceResourceId: workspaceResourceId } } } }] In this example, nsgFlowLogFilePath is a new parameter that you can use to specify the path to the parameter file you want to load. You can then pass different parameter files for different subscriptions when you deploy your Bicep file.

Hi @elias estevao Let me try this and get back to you if i have any doubt

Hi @elias estevao My question is in the path i have multiple files which belong to different subscription and different Resource Groups (individual file for each subscription and resource groups). And i want to load these individual files one by one from a single bicep. We don't want to use the pipeline variable to pass these values. Basically, we want to provide the names of the files in such a way so that we can dynamically call in loadjson. Here iam facing the problem on how i can frame the syntax to pickup the file dynamically in loadjson.

@Murali R

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well. I understand that you would like to load multiple parameter file(s) to your JSON template.

I believe @elias estevao answer is correct.

• In their template, instead of using nsgFlowLogFilePath parameter as String, you can use it as an array (containing paths of all the files which you would like to use).
• And then, use a Iterative loop to deploy all the flowlogs.
  • See example : https://video2.skills-academy.com/en-us/azure/azure-resource-manager/bicep/loops#array-elements
• This should become something like the below

param nsgFlowLogFilePaths array = [   './nsgFlowLogParameters/nsgFlowLogCLE_WESTEUROPE.json'
'./nsgFlowLogParameters/nsgFlowLogCLE_CENTRALINDIA.json'
'./nsgFlowLogParameters/nsgFlowLogCLE_EASTUS.json'
]

And the Looping part becomes,

resource flowLog 'Microsoft.Network/networkWatchers/flowLogs@2022-01-01' = [for nsgFlowLogFilePath in nsgFlowLogFilePaths : {
....
}]

Let me know how this goes.

Cheers,

Kapil.

HI @KapilAnanth-MSFT Thanks for the reply. In a Single Release Pipeline we have a different stages for each subscription. So if we load all the subscription json files in to one Bicep and trigger release will it not throw an error because one one json file will be relevant to the particular stage. If this will throw an error then how we can avoid that.