Skip to content

Conversation

@TaraGarg
Copy link
Contributor

@TaraGarg TaraGarg commented Aug 8, 2024

What this PR solves / how to test

Fixes https://jira.cfdata.org/browse/MQ-667

Author has addressed the following

@TaraGarg TaraGarg requested a review from a team as a code owner August 8, 2024 18:24
@changeset-bot
Copy link

changeset-bot bot commented Aug 8, 2024

🦋 Changeset detected

Latest commit: b56321b

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
Copy link
Contributor

github-actions bot commented Aug 8, 2024

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/10407109554/npm-package-wrangler-6450

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

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

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-wrangler-6450 dev path/to/script.js
Additional artifacts:
npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-create-cloudflare-6450 --no-auto-update
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-cloudflare-kv-asset-handler-6450
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-miniflare-6450
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-cloudflare-pages-shared-6450
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-cloudflare-vitest-pool-workers-6450
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-cloudflare-workers-editor-shared-6450
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10407109554/npm-package-cloudflare-workers-shared-6450

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


[email protected] includes the following runtime dependencies:

Package Constraint Resolved
miniflare workspace:* 3.20240806.0
workerd 1.20240806.0 1.20240806.0
workerd --version 1.20240806.0 2024-08-06

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

): Promise<QueueResponse> {
const accountId = await requireAuth(config);
return fetchResult(queuesUrl(accountId, queue_id), {
method: "PUT", // TODO: PATCH
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO?

Copy link
Contributor

@w-kuhn w-kuhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can update this to use the PATCH endpoint once it is merged & released

@petebacondarwin
Copy link
Contributor

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

@w-kuhn
Copy link
Contributor

w-kuhn commented Aug 13, 2024

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

once the API has this endpoint

@CarmenPopoviciu
Copy link
Contributor

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

once the API has this endpoint

@w-kuhn is there a timeline for this? Can this wrangler PR land before that API endpoint is up in prod?

@CarmenPopoviciu CarmenPopoviciu added the awaiting reporter response Needs clarification or followup from OP label Aug 15, 2024
@w-kuhn
Copy link
Contributor

w-kuhn commented Aug 15, 2024

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

once the API has this endpoint

@w-kuhn is there a timeline for this? Can this wrangler PR land before that API endpoint is up in prod?

This PR should land asap. Updating to use the new endpoint should happen as a fast follow.

@w-kuhn
Copy link
Contributor

w-kuhn commented Aug 15, 2024

can update this to use the PATCH endpoint once it is merged & released

But don't block this PR on that.

@TaraGarg
Copy link
Contributor Author

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

once the API has this endpoint

@w-kuhn is there a timeline for this? Can this wrangler PR land before that API endpoint is up in prod?

We are now waiting to make message expiration for queues available to everyone before we merge these wrangler CLI changes since we don't have something like a gate to only allow certain accounts in the workers-sdk changes.

@CarmenPopoviciu
Copy link
Contributor

CarmenPopoviciu commented Aug 15, 2024

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

once the API has this endpoint

@w-kuhn is there a timeline for this? Can this wrangler PR land before that API endpoint is up in prod?

We are now waiting to make message expiration for queues available to everyone before we merge these wrangler CLI changes since we don't have something like a gate to only allow certain accounts in the workers-sdk changes.

@TaraGarg so should I hold off merging these changes?

@TaraGarg
Copy link
Contributor Author

can update this to use the PATCH endpoint once it is merged & released

Do you mean once the API has this endpoint? Or once this PR here is merged?

once the API has this endpoint

@w-kuhn is there a timeline for this? Can this wrangler PR land before that API endpoint is up in prod?

We are now waiting to make message expiration for queues available to everyone before we merge these wrangler CLI changes since we don't have something like a gate to only allow certain accounts in the workers-sdk changes.

@TaraGarg so should I hold off merging these changes?

Yes please!

@CarmenPopoviciu CarmenPopoviciu removed the awaiting reporter response Needs clarification or followup from OP label Aug 15, 2024
@CarmenPopoviciu CarmenPopoviciu changed the title MQ-667: add queues update sub command [DO NOT MERGE] MQ-667: add queues update sub command Aug 15, 2024
@penalosa penalosa marked this pull request as draft November 12, 2024 23:58
@penalosa
Copy link
Contributor

Sounds like this is not ready to go, so moving to draft

@sdnts
Copy link
Contributor

sdnts commented Feb 12, 2025

Rebased and opened up a new PR here: #8120
This one can be closed (I don't have permissions to do that)

@penalosa penalosa closed this Jul 15, 2025
@github-project-automation github-project-automation bot moved this from In Review to Done in workers-sdk Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

7 participants