-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
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
feat: optionally send zone_id with a route #778
Conversation
🦋 Changeset detectedLatest commit: 8015ff3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
b2b80ff
to
c46671b
Compare
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2154535104/npm-package-wrangler-778 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/778/npm-package-wrangler-778 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/2154535104/npm-package-wrangler-778 dev path/to/script.js |
c46671b
to
2a188cf
Compare
This updates some dependencies. Some highlights - - updates to `@iarna/toml` means we can have mixed types for inline arrays, which is great for #774 / #778 - I also moved timeago.js to `devDependencies` since it already gets compiled into the bundle - updates to `esbuild` brings along a number of smaller fixes for modern js
This updates some dependencies. Some highlights - - updates to `@iarna/toml` means we can have mixed types for inline arrays, which is great for #774 / #778 - I also moved timeago.js to `devDependencies` since it already gets compiled into the bundle - updates to `esbuild` brings along a number of smaller fixes for modern js
This updates some dependencies. Some highlights - - updates to `@iarna/toml` means we can have mixed types for inline arrays, which is great for #774 / #778 - I also moved timeago.js to `devDependencies` since it already gets compiled into the bundle - updates to `esbuild` brings along a number of smaller fixes for modern js
2a188cf
to
632a853
Compare
632a853
to
184b547
Compare
aight, I think this is ready for a review/land. I'll work on adding |
184b547
to
33aa42d
Compare
@@ -327,15 +337,13 @@ export default async function publish(props: Props): Promise<void> { | |||
if (triggers && triggers.length) { | |||
deployments.push( | |||
fetchResult(`${workerUrl}/schedules`, { | |||
// TODO: Unlike routes, this endpoint does not support PATCH. | |||
// So technically, this will override any previous schedules. | |||
// We should change the endpoint to support PATCH. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this in the works, or no longer doable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using patch is weird because it means the source of truth is now coming from two places. But of course it means you can edit it in the dashboard. Each option has tradeoffs, but this is the one we're picking for now and can revisit later based on feedback.
Can confirm it works 🎉 Thanks so much for the quick work!
(now I can start to get working on this demo I'm giving in a few days...) |
Wonderful, good to hear |
This enables optionally passing a route as `{pattern: string, zone_id: string}`. There are scenarios where we need to explicitly pass a zone_id to the api, so this enables that. Some nuance: our toml parser unfortunately doesn't let you have mixed types in arrays, so if you have a single route with this special shape, then you'll have to do it for all of them. We can replace it with something more recent, but I'll do that in a subsequent PR. Further nuance: The errors from the api aren't super useful when invalid values are passed, but that's something to further work on. This also fixes some types in our cli parsing. Fixes #774
33aa42d
to
8015ff3
Compare
A followup to #778, this lets you send an optional `zone_name` with routes. This is particularly useful when using ssl for saas (https://developers.cloudflare.com/ssl/ssl-for-saas/).
A followup to #778, this lets you send an optional `zone_name` with routes. This is particularly useful when using ssl for saas (https://developers.cloudflare.com/ssl/ssl-for-saas/). Fixes #793
A followup to #778, this lets you send an optional `zone_name` with routes. This is particularly useful when using ssl for saas (https://developers.cloudflare.com/ssl/ssl-for-saas/). Fixes #793
A followup to #778, this lets you send an optional `zone_name` with routes. This is particularly useful when using ssl for saas (https://developers.cloudflare.com/ssl/ssl-for-saas/). Fixes #793
A followup to #778, this lets you send an optional `zone_name` with routes. This is particularly useful when using ssl for saas (https://developers.cloudflare.com/ssl/ssl-for-saas/). Fixes #793
A followup to #778, this lets you send an optional `zone_name` with routes. This is particularly useful when using ssl for saas (https://developers.cloudflare.com/ssl/ssl-for-saas/). Fixes #793
This enables optionally passing a route as
{pattern: string, zone_id: string}
. There are scenarios where we need to explicitly pass a zone_id to the api, so this is enables that.Some nuance: The errors from the api aren't super useful when invalid values are passed, but that's something to further work on.
This also fixes some types in our cli parsing.
Fixes #774