v3 release currently broken

[randomairborne]

action + repo When trying to run the worker, iI get an "Error: Action Failed"

Run cloudflare/wrangler-action@v3
  with:
    apiToken: ***
    workingDirectory: cdn-upload-worker
    command: publish --env staging
📥 Installing Wrangler
  Running command: npm install [email protected]
  npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
  ✅ Wrangler installed
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
🚀 Executing Wrangler Commands
  Error: 🚨 Action failed

[AlCalzone]

Maybe because the action is using wrangler v3, which doesn't have a publish command anymore, but deploy?
https://developers.cloudflare.com/workers/wrangler/commands/#deploy

[JacobMGEvans]

I should add stderr for more commands.

[JacobMGEvans]

Also a heads up with the new wrangler-action you should be able to consolidate these (once I figure out your bug)

      - name: deploy prod & dev
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          workingDirectory: "cdn-upload-worker"
          command:  | 
             deploy --config wrangler.prod.toml
             deploy --config wrangler.toml

[randomairborne]

ooh nice, thanks
let me know if you need anything else.

[randomairborne]

the issue was not publish

[JacobMGEvans]

the issue was not publish

It will be, the release PR will be merged soon #140

[randomairborne]

wait, publish is an issue?

[1000hz]

No, @JacobMGEvans mistook your comment to mean "cloudflare/wrangler-action was not published" rather than

- command: publish --env staging
+ command: deploy --env staging

not solving your problem.

We were ironing out some kinks with our release process earlier, hence the confusion. We've now released v3.0.2 with improved error logging when command fails, which should help us better understand what's causing problems with your action run. Would you mind re-running the job in your repo, @randomairborne?

[JacobMGEvans]

Thanks for clarifying Cina!

[randomairborne]

Ah, okay- now there is More than one account available but unable to select one in non-interactive mode.. I feel like this shouldn't be the case... i think my API token is only supposed to work for my personal account.

[randomairborne]

Yeah, only one account it added to this API token.

[JacobMGEvans]

What does your Wrangler.toml look like? You can replace the info on it with dummy data if its sensitive.

Oh I think I know how you can fix this.

- name: deploy prod & dev
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.AccoundID }}
          workingDirectory: "cdn-upload-worker"
          command:  | 
             deploy --config wrangler.prod.toml
             deploy --config wrangler.toml

Should look something like this test which is part of many accounts and has a scoped API Token too:

wrangler-action/.github/workflows/deploy.yml

Lines 60 to 74 in 93b26a6

	# END Setup and teardown of Worker Environment Tests
	# START Setup and teardown of Workers w/ Secrets Tests
	- name: Deploy app secrets w/ hardcoded Wrangler v2
	uses: ./
	with:
	wranglerVersion: "2.20.0"
	workingDirectory: "./test/base"
	apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
	accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
	secrets: |
	SECRET1
	SECRET2
	env:
	SECRET1: ${{ secrets.SECRET1 }}
	SECRET2: ${{ secrets.SECRET2 }}

[randomairborne]

Is this a limitation of the API, does it not allow you to check the scope of a token based on accounts? This specific token can only access one account.

[randomairborne]

btw, setting accountId does not fix the issue

[penalosa]

@randomairborne Could you link the GitHub Actions run with the accountId set to help us debug further?

[randomairborne]

It turns out I was setting it wrong, sorry.

[lrapoport-cf]

sounds like this has been resolved :) we will close for now, but please feel free to re-open if you are still running into issues!