WEBSITE_RUN_FROM_PACKAGE added automatically #290
hitensam
started this conversation in
Feature asks
Replies: 1 comment
-
|
Also, for me it additionally zip's the content. Not sure it decides to take a folder-based deployment, zip it, add this env variable and go. I thought it would determine based on what was set for the "package" what deployment type to do. My deployment is a credentials-based deployment, not a publish profile based one. Would be nice if it abided by the same rules as a profile-based deployment and look at the package type. This is a big deal for us as we use the IBM DB2 Connect package. That requires us to deploy functions in a folder-based state (not zip deploy). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I was using the
Azure/functions-action@v1GitHub Action to deploy my function app. While reviewing the deployment logs, I noticed that this action automatically sets theWEBSITE_RUN_FROM_PACKAGEkey, as seen in the GitHub Actions logs. Additionally, it also sets another environment variable:WEBSITE_ENABLE_SYNC_UPDATE_SITE.Is there a way to prevent the action from automatically setting these variables and allow only user-specified environment variables to be configured?
Beta Was this translation helpful? Give feedback.
All reactions