feat: support source deploy option #7169
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds an option to the Firebase CLI to override the
functions.source
config option onfirebase deploy
. This is much like the option which overrides the public directory when deploying to Hosting.The use case is where a user deploys a functions package whose structure is not supported by Firebase, such as a monorepo package. When deploying a functions package in a monorepo, a common strategy is to create a directory which contains the functions and other internal monorepo dependencies, and deploy that. One such example is isolate-package. Other strategies are mentioned in #653.
Scenarios Tested
firebase deploy --only functions --source apps/functions/deploy
, which deploys thedeploy
directory.firebase deploy --only functions
, which deploys the folder specified infirebase.json
.Sample Commands
firebase deploy --only functions --source apps/functions/deploy
firebase deploy --only functions -s apps/functions/deploy
firebase deploy --source apps/functions/deploy
firebase deploy -s apps/functions/deploy