Version secrets + secret behaviour changes

[WalshyDev]

What this PR solves / how to test

• Adds new versions secret commands (put, bulk, list and view).
• Adds a --pretty option to wrangler secret list
• Handles the new API error in rollback when attempting to rollback to a version with changed secrets from current

Author has addressed the following

• Tests
  • TODO (before merge)
  • Included
  • Not necessary because:
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required / Maybe required
  • Not required because:
• Changeset (Changeset guidelines)
  • TODO (before merge)
  • Included
  • Not necessary because:
• Public documentation
  • TODO (after merge - experimental features)
  • Cloudflare docs PR(s):
  • Not necessary because:

Screenshots

Version in dash

[changeset-bot]

🦋 Changeset detected

Latest commit: 3b660ad

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
wrangler	Minor
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-wrangler-5950

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/5950/npm-package-wrangler-5950

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-wrangler-5950 dev path/to/script.js

Additional artifacts:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-create-cloudflare-5950 --no-auto-update

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-cloudflare-kv-asset-handler-5950

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-miniflare-5950

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-cloudflare-pages-shared-5950

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9599437036/npm-package-cloudflare-vitest-pool-workers-5950

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.61.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20240610.1
workerd	1.20240610.1	1.20240610.1
workerd --version	1.20240610.1	2024-06-10

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[tanushree-sharma]

Nice one with the automated versions message! Can we add one on delete of a secret too?

Know you're still polishing up so ignore if these are on your to-do:

1. Only thing that should be updated / evaluated with the wrangler versions secret put command is secrets. Wrangler.toml warnings should not be shown

2. Copy when creating a new secret (Deleting a secret should reflect similar language)

? Enter a secret value: › ***
🌀 Creating the secret for Worker worker-name
✨ Success! Created version XXX with secret FOO.
➡️ To deploy this version with secret FOO to production traffic use the command wrangler versions deploy.```

[tanushree-sharma]

Looking great. Some more feedback:

1. Nit: Can we add a space between ➡️ and "To"

2. Forgot the flag in the copy
   ➡️ To deploy this version with secret new-secret to production traffic use the command wrangler versions deploy --x-versions.

3. Not seeing the version message populated anymore (I did wrangler secret put)

4. wrangler secret list is showing warnings (similar to wrangler dev #1 in my message above)

5. Not seeing updated output for wrangler versions view. Also shows the warning.

[CarmenPopoviciu]

thx Walshy :meouw-heart:

[tanushree-sharma]

Know this has already been merged but I have feedback:

1. Rollback guardrail: If we detect that a user is rolling back to a version that has a different value for a secret, we should warn the user but give them the option to proceed anyway:

I set up a case to hit the guardrail and wrangler is getting stuck here:

It isn't until I cancel the operation that I see the warning

Also, this is what I'm seeing in dash:

We need a popup window rather than a banner.

2. I want to make the next step after wrangler versions secret put/delete clear to users and the best way to do that is to have “To deploy..” on the next line

Instead of:

This:

3. Can we add back the automatic version message when a secret has been updated? Currently the version message is blank

4. Reminder to implement wrangler versions view updates