Open cfjedimaster opened 11 months ago
The issue appears to be because I had not set any keys yet. As soon as I do, it works, but obviously the result should have been something like, '0 keys set' or somesuch.
@cfjedimaster thanks for filing this issue. I just checked this behavior on Wrangler 3.28.1 and get the following:
I do think we should have some better messaging to indicate that there are no secrets set for the current worker.
cc: @dbenCF
I hit this too. FWIW I added a secret, listed it, deleted it and then I got back []
so its related to a new project with no secrets ever added yet.
I also don't understand where these go in the UI - I had tried adding them there first and they are not listed, and when I add them via the cli they are also not in the UI.
Which Cloudflare product(s) does this pertain to?
Workers Runtime
What version(s) of the tool(s) are you using?
3.9.0
What version of Node are you using?
20.0.0
What operating system are you using?
WSL
Describe the Bug
In a worker project, tried to get my secrets by using
npx wrangler secret list
, and I get:I confirmed via
npx wrangler whoami
that I am logged in.Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response