Passing tags parameter

[RobBowman]

Does anyone have an example of calling the "GenerateResourcesAndImage" function and passing tags to be used when creating the azure resources please? The problem I'm facing is I'm getting back an error from Azure policy like this:

policyDefinition":{"name":"Require a tag on resource groups

This is what I've tried:

$tagsJson = '{"BusinessUnit":"IDS", "ProductName":"DevOpsAgent", "Environment":"Production"}'
$tagsHashtable = ($tagsJson | ConvertFrom-Json -AsHashtable)
GenerateResourcesAndImage -SubscriptionId sub-id-here -ResourceGroupName rg-name-here -AzureLocation "UK South" -ImageType "UbuntuMinimal" -Tags $tagsHashtable

It gives the following error:

on <value for var.azure_tags from arguments> line 1:
  (source code not available)

Variables may not be used here.

Error: Variables not allowed

[vpolikarpov-akvelon]

Hi @RobBowman. I tried to reproduce your issue, but didn't succeed. Did you make any changes to scripts or templates before trying to run this?

[tdysko-cf]

I got the same result no modifications done on scripts

[vpolikarpov-akvelon]

Hey @tdysko-cf. Could you provide exact commands you executed and Powershell version?

[tdysko-cf]

hi @vpolikarpov-akvelon sorry for the delay, simply clone the repo run GenerateResourcesAndImage -Tags @{tag_one= "test"; environment= "test"; application_name = "test"} just pick the ubuntu2204 or ubuntu minimal. Something is wrong with HCL.

I was only able to pass that tags variable through an environment variable like this:
$env:PKR_VAR_azure_tags = '{ tag_one = "test", environment = "qa", application_name = "vmss"}'
Passing it through CLI variables, like it's done in GenerateResourcesAndImage failed.

[vpolikarpov-akvelon]

Hey @tdysko-cf. I finally realised what causes this issue. I've fixed it in #8058. Could you please update your fork or local repo from main branch and try again?

[tdysko-cf]

looks good now, thanks!

[vpolikarpov-akvelon]

Hey @RobBowman @tdysko-cf.
JFYI: We rewrote image generation script recently (#8065). We implemented a lot of improvements and migrated from Az Powershell module to CLI tool. It should be backwards compatible. Feel free to reach out if you have any problems with the new version.

[RobBowman]

Thanks @vpolikarpov-akvelon it is working ok now