Hi, I have a question related to the github action. I run:

- name: Publish provider contract on passing test run
        uses: pactflow/actions/publish-provider-contract@v1.2.0
        env:
          oas_file: ${{ env.OPENAPI_FILE }}
          results_file: ${{ env.CHANGELOG_FILE }}
          version: ${{ steps.prepare-env.outputs.version }}
          PACT_BROKER_TOKEN: ${{ env.TOKEN_IDP_PACTFLOW }}

but I get this error about the

yaml

file being missing:

Status: Downloaded newer image for pactfoundation/pact-cli:latest
/usr/lib/ruby/gems/3.2.0/gems/pact_broker-client-1.75.1/lib/pactflow/client/cli/provider_contract_commands.rb:75:in `read': No such file or directory @ rb_sysopen - openapi.yaml (Errno::ENOENT)
	from /usr/lib/ruby/gems/3.2.0/gems/pact_broker-client-1.75.1/lib/pactflow/client/cli/provider_contract_commands.rb:75

but the file is definitely there. Is there a way to confirm the execution path of the task, or something?

it volumes mounts from the root of your workspace, have you checked out your codebase beforehand? can you share more of your workflow? and ls the workspace prior to running the publish step? you can sh into the docker container so you could run something like

docker run --rm \
  -w ${PWD} \
  -v ${PWD}:${PWD} \
  -e PACT_BROKER_BASE_URL=$PACT_BROKER_BASE_URL \
  -e PACT_BROKER_TOKEN=$PACT_BROKER_TOKEN \
  pactfoundation/pact-cli:latest sh -c 'ls'

ah so the code run in a github action. I can make this work from local, no problem, but in a GHA using

uses: pactflow/actions/publish-provider-contract@v1.2.0

it fails. I run this in the action, as mentioned:

- name: Publish provider contract on passing test run
        uses: pactflow/actions/publish-provider-contract@v1.2.0
        env:
          oas_file: ${{ env.OPENAPI_FILE }}
          results_file: ${{ env.CHANGELOG_FILE }}
          version: ${{ steps.prepare-env.outputs.version }}
          PACT_BROKER_TOKEN: ${{ env.TOKEN_IDP_PACTFLOW }}

ls

the workspace prior to running the publish step to confirm env.OPENAPI_FILE is indeed available at the working directory

yes, it is available, is not empty, and has the correct values and name 😞 I’ll try to run it via a normal sh script calling docker, as it does under the hood, to compare