Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed "WEBSITE_RUN_FROM_PACKAGE true" to "WEBSITE_RUN_FROM_PACKAGE 1" #16576

Merged
merged 8 commits into from
Jul 27, 2022
Merged

Changed "WEBSITE_RUN_FROM_PACKAGE true" to "WEBSITE_RUN_FROM_PACKAGE 1" #16576

merged 8 commits into from
Jul 27, 2022

Conversation

CodingIsBliss
Copy link
Contributor

Task name: Deploy task

Description: As per the documentation for the setting WEBSITE_RUN_FROM_PACKAGE from https://docs.microsoft.com/en-us/azure/azure-functions/run-functions-from-deployment-package the value needs to be 1 to be enabled. the value 'true' does not work.

Documentation changes required: N

Added unit tests: N

Attached related issue: N

Checklist:

  • Task version was bumped - please check instruction how to do it
  • Checked that applied changes work as expected

@FinVamp1
Copy link
Contributor

As discussed offline.

I have apps that have been deployed with WEBSITE_RUN_FOM_PACKAGE = true and it still does work.

I do agree with you that we should have this been consistent with the documentation.

If you didn’t mind however I would like to include this change in the V2 version of the task which I am hoping to merge soon.

azure-pipelines-tasks/Tasks/AzureFunctionAppV2 at users/finvamp1/FunctionsAppv2 · microsoft/azure-pipelines-tasks (github.com)

@CodingIsBliss
Copy link
Contributor Author

CodingIsBliss commented Jul 15, 2022

As discussed offline.

I have apps that have been deployed with WEBSITE_RUN_FOM_PACKAGE = true and it still does work.

I do agree with you that we should have this been consistent with the documentation.

If you didn’t mind however I would like to include this change in the V2 version of the task which I am hoping to merge soon.

azure-pipelines-tasks/Tasks/AzureFunctionAppV2 at users/finvamp1/FunctionsAppv2 · microsoft/azure-pipelines-tasks (github.com)

Hi @FinVamp1 ,

The behavior of how the app is being run is quite different when the value of WEBSITE_RUN_FOM_PACKAGE is '1' vs when it is not. Nevertheless, the app will run!

When it is not '1' zipdeploy will basically extract the zip file into the wwwroot folder. When the value is '1' the zipfile is not extracted into the wwwroot folder but rather mounted to wwwroot at runtime and the wwwroot will be readonly. This will effectively reduce the deployment time.

I would suggest keeping this value as 1.

Thanks,
Sarath

@tomaeda
Copy link

tomaeda commented Jul 19, 2022

Hello, @CodingIsBliss and @FinVamp1
Changing WEBSITE_RUN_FROM_PACKAGE to true causes an error and some users have their deployment blocked.
I think this PR may be able to resolve the issue, please can you see #16005 and #15983 ?

Copy link
Contributor

@FinVamp1 FinVamp1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@FinVamp1
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@FinVamp1 FinVamp1 merged commit 0ff76db into microsoft:master Jul 27, 2022
@awarberg
Copy link

awarberg commented Nov 24, 2022

We are experiencing issues with Elastic Premium Plan after this switch from expanded/wwwroot zip deploy to run from package. SyncTriggers sometimes fails to run and we now need to 1) notice that this happened (in the Activity Log of each Function App) and 2) manually run SyncTriggers per affected Function App.

The wwwroot zip deploy automatically sync's trigger information and we suspect this is why we didn't notice this problem until now.

@CodingIsBliss Is it possible to override the deployment strategy for Elastic Premium Plan so that it uses the wwwroot zip deploy strategy like before this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants