Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

Allow users to specify worker directory when running wrangler publish #482

Closed
gabbifish opened this issue Aug 27, 2019 · 5 comments
Closed
Labels
feature Feature requests and suggestions timed out

Comments

@gabbifish
Copy link
Contributor

gabbifish commented Aug 27, 2019

💡 Feature request

Overview and problem statement

There are Wrangler users that may use workers in a monorepo; that is, they will have multiple generated workers in one repository. This means that, for actions like CI, wrangler publish may be run on a specific worker within a monorepo. This is a case where providing an optional path argument for wrangler publish may be useful.

Basic example

Include a basic code example of this new feature if possible. Omit this section if not applicable.
Let's say we have a repo with multiple generated workers directories:

.
├── a
└── b

If we want to deploy the worker in directory a from the root of this repo, we would run

$ wrangler publish a

If we are just deploying from a worker directory, the preexisting wrangler publish invocation should still work.

@gabbifish gabbifish added user report feature Feature requests and suggestions and removed user report labels Aug 27, 2019
@EverlastingBugstopper
Copy link
Contributor

+1

@stale
Copy link

stale bot commented Jul 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Sep 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Jan 9, 2022

This issue has been automatically marked as stale because it has not had recent activity in the last 180 days. It will be closed if no further activity occurs in the next week. Please feel free to comment if you'd like it to remain open, and thank you for your contributions.

@stale stale bot added the timed out label Jan 9, 2022
@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically closed because it has not had recent activity. You may re-open the issue if it is still relevant.

@stale stale bot closed this as completed Mar 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Feature requests and suggestions timed out
Projects
None yet
Development

No branches or pull requests

4 participants