search

Azure / azure-functions-host

The host/runtime that powers Azure Functions
https://functions.azure.com
MIT License
1.92k stars 441 forks source link

extensions.csproj in the functions-extensions folder cause rest of function files not to be copied to wwwroot on ci/cd deployment #2791

Open peteroden opened 6 years ago

peteroden commented 6 years ago

when function extensions are installed the extensions.csproj is copied and built in the functions-extensions folder. It works perfectly this way when run locally, but when it is deploy using github ci/cd the rest of the files of the function app are never copied out of the repository folder.

Investigative information

Repro steps

  1. Using Functions CLI on MacOS
  2. Install an extension such as: func extensions install -p Microsoft.Azure.Webjobs.Extensions.CosmosDB -v 3.0.0-beta7
  3. deploy the function to azure using github ci/cd

Expected behavior

the extensions.csproj would be processed an installed and all the other files would be copied from the repo folder into the wwwroot folder

Actual behavior

since the kudu script is expecting the extensions.csproj to be in the root folder it only copies the extensions bin folder and not the rest of the function thus none of the functions in the function app are accessible

Known workarounds

copy the extensions.csproj file to the root function app folder and delete the functions-extensions folder

Related information

pragnagopa commented 6 years ago

@mathewc - Can you please take a look?

anthonychu commented 6 years ago

Is this an issue for azure-functions-core-tools? Seems to be the CLI that keeps insisting on creating the extensions.csproj file in the function-extensions folder whenever func extensions install or func extensions sync are run. @ahmelsayed @fabiocav

fabiocav commented 6 years ago

It is rooted on that issue (although there's another problem at play). We've had that tracked for a while and since we'll be working on a Core Tools release today, I'll just have that fixed quickly before we push those bits out.

fabiocav commented 6 years ago

Problem was fixed. Will go live on the next release. That had been fixed before and was somehow regressed.