BICEP Output Variables Issue

[rlittler]

I am capturing bicep output params on my pipeline agent as per my YAML AzureCLI@2 task. I then try to reference the output var in the subsequent AzurePowershell@4 task:

'-Workspace $(bicepOutputs.LogAnalyticsWorkspaceId) -RulesFile sentinelArtefacts/sentinelAnalyticsRules/analyticsRules.json'

I can see the vars being stored

However, when my subsequent PS4 task tries to run, I receive the following error:

For reference: this is my PS script I am calling and passing my output var to:

Any ideas? :)

[GABRIELNGBTUC]

This has nothing to do with bicep.

ADO pipeline variables only support strings and integers as values. If you need to pass the LAW id in another task, you must retrieve it with powershell and register it to an ADO variable

[brandonlittler]

I think this is possible? as per:

#4638

[GABRIELNGBTUC]

Sorry I misread your initial script and didn't notice the set variable function was inside a loop.

The structure $(bicepOutputs.LogAnalyticsWorkspaceId) is looking for a variable named LogAnalyticsWorkspaceId created by the task bicepOutputs.

Looking at your output, you can see that every variable name is prepended with out. You then have to use bicepOutputs.outLogAnalyticsWorkspaceId to resolve to an existing variable

[microsoft-github-policy-service]

Hi @rlittler, this issue has been marked as stale because it was labeled as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. Thanks for contributing to bicep! 😄 🦾