compile bicep files

[lipalath-ms]

I have the following step for compiling bicep file and creating json file and publishing artifact. This step is repeated in multiple stages in order to compile multiple bicep files and create json files in multiple locations in the artifact and is very time consuming. Is there an alternate way to deploy using bicep file and avoid compilation?

 - powershell: |
              $bicepTemplates = Get-ChildItem -Filter "template.bicep" -Recurse
              foreach($template in $bicepTemplates)
              {
                az bicep build --file $template.FullName
              }
   displayName: 'Compile Bicep templates'

 - task: PublishBuildArtifacts@1
   displayName: 'publish artifact'
   inputs:
        PathtoPublish: '$(build.artifactstagingdirectory)'
        ArtifactName: '$(Build.BuildNumber)'

And this json file is used for deployment:

- task: AzureResourceGroupDeployment@2
  displayName: 'deploy private persistent data'
  inputs:
    azureSubscription: ${{parameters.serviceConnection}}
    resourceGroupName: ${{parameters.solutionAbbreviation}}-data-${{parameters.environmentAbbreviation}}
    csmFile: ${{ parameters.root }}/Infrastructure/data/private/template.json
    csmParametersFile: ${{parameters.root}}/Infrastructure/data/private/parameters/parameters.${{parameters.environmentAbbreviation}}.json
    overrideParameters: '-environmentAbbreviation "${{parameters.environmentAbbreviation}}" -location "${{parameters.location}}" -solutionAbbreviation "${{parameters.solutionAbbreviation}}" -tenantId "${{parameters.tenantId}}" '
    deploymentMode: 'Incremental'

[kevball2]

You no longer need to run the az Bicep build command to convert your templates to ARM. The AzureResourceGroupDeployment@2 task will do this for you.

[brwilkinson]

confirming is the the solution, except they also bumped the version to 3 AzureResourceManagerTemplateDeployment@3

[lipalath-ms]

@kevball2 I updated this task to use bicep instead of json:

- task: AzureResourceGroupDeployment@2
  displayName: 'deploy private persistent data'
  inputs:
    azureSubscription: ${{parameters.serviceConnection}}
    resourceGroupName: ${{parameters.solutionAbbreviation}}-data-${{parameters.environmentAbbreviation}}
    **csmFile: ${{ parameters.root }}/Infrastructure/data/private/template.bicep**
    csmParametersFile: ${{parameters.root}}/Infrastructure/data/private/parameters/parameters.${{parameters.environmentAbbreviation}}.json
    overrideParameters: '-environmentAbbreviation "${{parameters.environmentAbbreviation}}" -location "${{parameters.location}}" -solutionAbbreviation "${{parameters.solutionAbbreviation}}" -tenantId "${{parameters.tenantId}}" '
    deploymentMode: 'Incremental'

but I get this error:

##[error]Check out the troubleshooting guide to see if your issue is addressed: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting
##[error]Error: Ensure the Template file ( 'D:\a\1\2.0.2206.389_debug\Infrastructure\data\template.bicep' ) is valid. Task failed while parsing with following error: Unexpected token @ in JSON at position 0

[mrblackistone]

I have this same issue with the AzureResourceGroupDeployment@3 task in Azure DevOps Server 2020. It refuses to parse bicep files and tries unsuccessfully to parse them as JSON, choking on the "@" decorator or "p" in "param" or whatever else it encounters first that isn't an open brace.

[brwilkinson]

@mrblackistone please confirm you have the latest version of az cli or az powershell installed, also the latest Bicep.exe version.

Depending on how you are managing your servers.

[mrblackistone]

@mrblackistone please confirm you have the latest version of az cli or az powershell installed, also the latest Bicep.exe version.

Depending on how you are managing your servers.

@brwilkinson The same thing occurs in Azure DevOps, where the servers are Microsoft's own hosted pool. Both the AzureResourceManagerTemplateDeployment@3 and the AzureResourceGroupDeployment@2 task have the same result.

Using AzureResourceManagerTemplateDeployment@3:
##[error]Error: Ensure the Template file ( 'Unexpected token @ in JSON at position 0' ) is valid. Task failed while parsing with following error: %s

Using AzureResourceGroupDeployment@2:
##[error]Error: Ensure the Template file ( 'Unexpected token @ in JSON at position 0' ) is valid. Task failed while parsing with following error: %25s

[anthony-c-martin]

@mrblackistone: is this still a problem? If so, could you raise an issue for this here and tag me: https://github.com/microsoft/azure-pipelines-tasks/issues

[mrblackistone]

This now works in the AzureResourceManagerTemplateDeployment@3 task on both Azure DevOps using Microsoft's default Windows pool, and on Azure DevOps server using our own self-hosted pool. Previously both had the same issue. The task version didn't change, so I don't know what's different now. I did not yet confirm using the AzureResourceGroupDeployment@2 task, and won't since the other task now works.