-
Notifications
You must be signed in to change notification settings - Fork 337
wrangler publish has inconsistent behavior #388
Comments
I find the Thinking about #385, I do wonder if it might make sense to just become very explicit about zoned deploy targets. Publishing with Makes me wonder if it would make sense to deprecate the |
I would also quite like that, I find the |
I think introducing |
we think this will be mostly addressed by the work being done in the Environments milestone; however, there may still be some surprising behavior if users deviate from best practices. Should reassess after Environments is released. |
Steps to reproduce
wrangler generate <name here>
Use a name that isn't used currently, as wrangler will overwrite an existing one.name
,route
,zone_id
,account_id
, andprivate=true
inwrangler.toml
.wrangler publish
output says
worker was successfully published
but it only appears in the editor UI and isn't actually published anywhere. this is issue Unclear messaging of wrangler publish #357.wrangler publish --release
output says
worker was successfully published. You can view it at <route>
. which is True.wrangler publish
output says
worker was successfully published
but in reality, the script running at route was also updated without passing in the--release
flag. This is confusing.The text was updated successfully, but these errors were encountered: