Resolve dockerfile path based on original, non-redirected config path#10005
Resolve dockerfile path based on original, non-redirected config path#10005emily-shen merged 1 commit intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 4d4646b The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 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 |
|
Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the Depending on your changes, running Notes:
|
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: |
0d98db5 to
db182fd
Compare
db182fd to
4d4646b
Compare
dario-piotrowicz
left a comment
There was a problem hiding this comment.
Looks good to me 😄
(just left a couple of very minor comments 🙂)
| imageTag: string, | ||
| dryRun: boolean, | ||
| pathToDocker: string, | ||
| /** The original (non-redirected) user config path */ |
There was a problem hiding this comment.
what about renaming the parameter userConfigPath to avoid possible future confusion? 🤔
There was a problem hiding this comment.
ah that's probably better, but this needs to go out in the next release so i'm just going to kick this one through as is - sorry!
| expect(std.warn).toMatchInlineSnapshot(`""`); | ||
| }); | ||
|
|
||
| it("resolve the dockerfile based on the non-redirected userConfigPath rather than the actual config path", async () => { |
There was a problem hiding this comment.
| it("resolve the dockerfile based on the non-redirected userConfigPath rather than the actual config path", async () => { | |
| it("resolve the dockerfile based on the non-redirected userConfigPath rather than the redirected config path", async () => { |
🤔 ?
This reverts commit 64d71b1.
…name matches its own Worker name removing try catch since error gets thrown either way use userConfigPath instead of redirected one (#10005) Revert "use userConfigPath instead of redirected one (#10005)" This reverts commit 5c11fe7504a0b16a963c726cc63748426fd8bab6. fix deep import prettier run fix: make vitest-pool-workers not break if Workflow binding's script_name matches its own Worker name
…hes its own Worker name (#10033) * fix: make vitest-pool-workers not break if Workflow binding's script_name matches its own Worker name removing try catch since error gets thrown either way use userConfigPath instead of redirected one (#10005) Revert "use userConfigPath instead of redirected one (#10005)" This reverts commit 5c11fe7504a0b16a963c726cc63748426fd8bab6. fix deep import prettier run fix: make vitest-pool-workers not break if Workflow binding's script_name matches its own Worker name * apply suggestions from code review * code review suggestion: delete script_name instead of replacing it
userConfigPath is the path of the original wrangler config, while configPath could point to a redirected wrangler config. We should resolve the dockerfile and build context based on the original config's path. This makes sure containers can be deployed if the app has been built by the vite plugin.