Mismatch between readme functionality and actually implemented functionality for arg 'buildArguments'

[nath3lf]

Error Details:

The readme lists the following argument as valid within the confines of a workflow.

buildArguments

No

A list of build arguments provided as KEY=VALUE pairings and are space-separated. If a Dockerfile has been provided or is discovered in the application source, each build argument will be passed to the docker build command via the --build-arg flag. If the Oryx++ builder is used to create a runnable application image, each build argument will be passed to the pack build command via the --env flag.

When I use the workflow file like below, the workflow is invalid. Upon examining the workflow action.yaml - this input is not even supported.

  - name: Build and deploy Container App
    uses: azure/container-apps-deploy-action@v1
    with:
      ...
      buildArguments: |
        "IMAGE_SHA_ARG=${{ env.IMAGE_SHA }}"

[bjarkehs]

In case other people also run into this issue. The docs mention buildArguments but it's only supported in v2. If you change:

uses: azure/container-apps-deploy-action@v1

to

uses: azure/container-apps-deploy-action@v2

it'll work 👍

Hopefully the PR #114 that clears up this confusion will be merged soon