Specifying collection & environment via Postman API GUID not working

[capelio]

When running the following job:

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: matt-ball/newman-action@v1.0.4
        with:
          apiKey: ${{ secrets.POSTMAN_API_KEY }}
          collection: 2d8b8a29-29a7-4a70-8db7-615ad8e44874
          environment: 3d1532d7-22bd-4d50-99ea-4e66144530fd

I'm seeing the following error:

Newman run failed! Error: collection could not be loaded
  unable to read data from file "2d8b8a29-29a7-4a70-8db7-615ad8e44874"
  ENOENT: no such file or directory, open '2d8b8a29-29a7-4a70-8db7-615ad8e44874'

Any thoughts on why Newman's interpreting the GUIDs as file paths?

[matt-ball]

Looks like you might have the ID rather than UID - how are you retrieving it? The info tab in the Postman app is one place to grab it.

[capelio]

Odd, I grabbed them using calls to the Postman API with curl as the README suggested, but you're right. When I compare the API-returned values to what's in the info tab in the UI, the values are different. I'll try the new values and see if they work.

[capelio]

Ok, so I found the root of the problem. When using the API to get the IDs, there are two ID fields: id and uid. Once I used jq to pretty-print the API response, I noticed the two right away.

I'll open a quick PR against the README to add another sentence or two calling out the distinction.

[capelio]

#53

[matt-ball]

Looks good - thanks. Let me just check we can't make this work with either option, as then it'd be super straight-forward for everyone. I might've made things too specific.