You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
According to the documentation, we can use the --copyToOutput flag to copy all needed files to the .funcpack directory and then publish from there. It gives the following example:
However when I tried this approach, it still published the entire parent directory to Azure instead of the content in .funcpack only. Is it the right behavior? Then why we need to publish within .funcpack?
My steps:
Created a new function app called func-test
Created a new TimerTrigger function
Ran pack & publish as shown above
Publish <path>\func-test contents to an Azure Function App. Locally deleted files are not removed from destination.
Getting site publishing info...
Creating archive for current directory...
Uploading archive...
Upload completed successfully.
When I created a host.json file in the .funcpack directory and published again, it attempted to publish from .funcpack but failed due to Error calling sync triggers:
Getting site publishing info...
Creating archive for current directory...
Uploading archive...
Error calling sync triggers (InternalServerError).
Retry: 1 of 2
Creating archive for current directory...
Uploading archive...
Error calling sync triggers (InternalServerError).
Retry: 2 of 2
Creating archive for current directory...
Uploading archive...
Error calling sync triggers (InternalServerError).
The text was updated successfully, but these errors were encountered:
I see the same behavior for your step 1-3. The function is uploaded, but it's the original version of the function app, not the packed version - looking in the portal, the .funcpack folder does not appear to have been uploaded.
Version information:
Azure Functions Core Tools (2.0.1-beta.24)
Function Runtime Version: 2.0.11587.0
funcpack -V: 1.0.0
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
According to the documentation, we can use the
--copyToOutput
flag to copy all needed files to the.funcpack
directory and then publish from there. It gives the following example:However when I tried this approach, it still published the entire parent directory to Azure instead of the content in
.funcpack
only. Is it the right behavior? Then why we need to publish within.funcpack
?My steps:
func-test
When I created a host.json file in the
.funcpack
directory and published again, it attempted to publish from.funcpack
but failed due toError calling sync triggers
:The text was updated successfully, but these errors were encountered: