Is it possible to use deployer() in .bicepparam?

[guimatheus92]

The way I use Bicep is to create a .bicep template file and then create a .bicepparam for parameters only.
From Release v0.32.4 is now possible to get the deployer id, and I was thinking to add in Tags to facilitate the control of it. But I noticed it only works in Template file.

Is there a way to add that function deployer() in parameters instead?

This is an example of parameter file I use:

using '../../Templates/StorageAccount.Template.bicep'

param __storageAccountName = 'demosa1eastus2'
param __location = 'eastus2'
param __storageAccountSkuName = 'Standard_LRS'
param __storageAccountKind = 'StorageV2'
param __storageAccountContainers = ['mockcon1', 'mockcon2']
param __tags = {
  'Department': 'Finance'
  'Project': 'Migration'
  'Description': 'Sample SA'
  'ResourceAliasName': 'SA1'
  'Version': '0.0.0.0'
  'ResourceUpdateDatetime': ''
  'Deployer': deployer().objectId
}

[jeskew]

Functions that report metadata about the deployment (resourceGroup(), subscription(), tenant(), deployer(), providers(), etc.) aren't currently usable within a .bicepparam file because they get evaluated before the deployment starts.

You can use deployer() in a variable value or parameter default in a template if that helps. The value can then be merged into the __tags parameter.

[guimatheus92]

Oh I see, in that case how can I add that to an existing tags pararmeter then please? If you dont mind sharing an exemple here @jeskew

[jeskew]

You could do something like the following in the template:

param __tags object

var tagsWithDeployer = {
  ...__tags
  Deployer: deployer().objectId
}

[guimatheus92]

Thanks! Now I just need to check how to apply in multiple bicep files 🤌