-
Notifications
You must be signed in to change notification settings - Fork 1k
Adds the --force-subdomain-deploy
flag to the wrangler triggers deploy
command
#10549
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
Adds the --force-subdomain-deploy
flag to the wrangler triggers deploy
command
#10549
Conversation
🦋 Changeset detectedLatest commit: 962f91d The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
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 |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
wrangler
commit: |
24c5b94
to
8606513
Compare
routes: Route[], | ||
deployments: Array<Promise<string[]>> | ||
deployments: Array<Promise<string[]>>, | ||
forceSubdomainDeploy: boolean |
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.
Do we really need to add an arg, given that we pass props.forceSubdomainDeploy
and props is already the first arg?
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.
I feel like it is good to be explicit about forcing here. I want to get rid of props
arg eventually.
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.
Could you please reconsider this for now?
You can still explicitly pass props.forceSubdomainDeploy
later at the time you refactor the code.
8606513
to
46b317e
Compare
--force-subdomain-deploy
flag to the wrangler triggers deploy
command
46b317e
to
82b8bf8
Compare
Wrangler will sometimes skip the API call if the config file matches the remote state. However, we need to be able to force it in some cases.
82b8bf8
to
962f91d
Compare
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.
We need tests even for experimental command
We did some changes in the API that should make this flag less urgent. |
Wrangler will sometimes skip the API call if the config file matches the remote state. The flag lets us skip this behavior, and force the subdomain deployment.
Follow up of: #10478
Describe your change...
Adds
--force-subdomain-deploy
flag towrangler triggers deploy
.