We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrangler
3.87.0 [Wrangler]
22.11.0
MacOS Sonoma 14.7
wrangler secret bulk does not log why it fails, including when the secret name is already in use by another binding type:
wrangler secret bulk
This is causing user confusion: cloudflare/wrangler-action#240
When the name of a secret conflicts with another binding or environment variable, it should log why, similar to how wrangler secret put does:
wrangler secret put
MY_VAR
./secrets.json
{"MY_VAR": "my secret"}
wrangler secret bulk ./secrets.json
https://github.com/jahands/wrangler-action-example/tree/bulk-put-repro
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Which Cloudflare product(s) does this pertain to?
Wrangler
What version(s) of the tool(s) are you using?
3.87.0 [Wrangler]
What version of Node are you using?
22.11.0
What operating system and version are you using?
MacOS Sonoma 14.7
Describe the Bug
Observed behavior
wrangler secret bulk
does not log why it fails, including when the secret name is already in use by another binding type:This is causing user confusion: cloudflare/wrangler-action#240
Expected behavior
When the name of a secret conflicts with another binding or environment variable, it should log why, similar to how
wrangler secret put
does:Steps to reproduce
MY_VAR
./secrets.json
:{"MY_VAR": "my secret"}
wrangler secret bulk ./secrets.json
Please provide a link to a minimal reproduction
https://github.com/jahands/wrangler-action-example/tree/bulk-put-repro
Please provide any relevant error logs
No response
The text was updated successfully, but these errors were encountered: