Request for documentation: How to use GitHub Actions Variables as Parameters?

[boldandbusted]

Howdy. In the azure/arm-deploy Action (now deprecated), you could have parameters like this:

          parameters: >
            location=${{ vars.AZURE_LOCATION }}
            gitHubAppKey="${{ secrets.GH_APP_PRIVATE_KEY }}"

How can you do something similar with azure/bicep-deploy, since parameters: is now a JSON object? Or is this currently supported and under-documented? Thanks!

[MirzaMerdovic]

@boldandbusted you probably saw this ,but just in case there is an example here

- name: Deployment
  uses: azure/bicep-deploy@v2
  with:
    type: deployment
    operation: create
    name: Development
    scope: resourceGroup
    subscription-id: 00000000-0000-0000-0000-000000000000
    resource-group-name: example
    template-file: ./src/main.bicep
    parameters: '{"name": "Development", "tags": { "environment": "development" }}'

What is not clear to me is whether this can be used in combination with parameters-file and will parameters then override value in parameters-file, basically I don't understand how parameter precedence works here but maybe that's not important for you

[boldandbusted]

@boldandbusted you probably saw this ,but just in case there is an example here

- name: Deployment
  uses: azure/bicep-deploy@v2
  with:
    type: deployment
    operation: create
    name: Development
    scope: resourceGroup
    subscription-id: 00000000-0000-0000-0000-000000000000
    resource-group-name: example
    template-file: ./src/main.bicep
    parameters: '{"name": "Development", "tags": { "environment": "development" }}'

What is not clear to me is whether this can be used in combination with parameters-file and will parameters then override value in parameters-file, basically I don't understand how parameter precedence works here but maybe that's not important for you

I think that is a different question than mine. :)

[anthony-c-martin]

Howdy. In the azure/arm-deploy Action (now deprecated), you could have parameters like this:

          parameters: >
            location=${{ vars.AZURE_LOCATION }}
            gitHubAppKey="${{ secrets.GH_APP_PRIVATE_KEY }}"

How can you do something similar with azure/bicep-deploy, since parameters: is now a JSON object? Or is this currently supported and under-documented? Thanks!

As of the latest release, YAML and JSON are both supported for complex values. My preferred approach would be:

- name: Deployment
  uses: azure/bicep-deploy@v2
  with:
    type: deployment
    ...
    parameters: |
      location: ${{ vars.AZURE_LOCATION }}
      gitHubAppKey: ${{ secrets.GH_APP_PRIVATE_KEY }}

[SydneyhSmith]

My understanding is the todo here is to add the YAML support to our docs/ReadMe and examples to add YAML examples

[renrutsirhc]

@SydneyhSmith It would also be great if the docs could clarify how to combine (with clear info and examples given about how precedence works when combining parameters from various sources):

1. multiple parameters files
2. parameters file and inline parameters
3. multiple parameters files and inline parameters