-
Notifications
You must be signed in to change notification settings - Fork 171
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
Unable to deploy .NET 7 Isolated via App Service Build Service #1865
Unable to deploy .NET 7 Isolated via App Service Build Service #1865
Comments
@mattchenderson Who can help with deployment center(in portal) related issues? |
@kulkarnisonia16 for deployment center and tools |
It is recommended to use the "GitHub" option from the deployment center, instead of "External Git". It will help you configure a GitHub action workflow which is more reliable and uses this deployment action: https://github.com/Azure/functions-action |
@patelchandni , in many scenarios (like the one I'm currently in, which is allowing people to deploy DfMon with an ARM template) deploying with GitHub actions is not an option, as it requires you to have full control over the repo, which many people don't have or don't want to have. Are you saying that App Service Build Service is now deprecated (because I haven't seen any announcements like that) ? |
Im escalating and will take a look and assign. If zip is bad suspect this is somewhere in the deployment center package build. |
@scale-tone Here is a PR for it: The root issue triggering the Deployment center bug is there's no solution file, and then Deployment Center assumes this is a vanilla web app, and not a function, during the deployment build. |
I have the same problem with a .NET 8 Isolated function being zip deployed through a Bamboo plan via Azure CLI. Build log without .sln file
After i added the solution file the Deployment Center seems to understand that it is a function and seems to build correctly. See attached log The function seems to be built directly to the wwwroot folder as expected: However the deploy seems to somehow break the Function App resource. Here are the overview before deployment: After deployment there is an error Trying to call the functions gives a 503 response saying These are the appSettings declared in the ARM template:
Edit |
Thanks for your help, @paulyuk . When deploying something that isn't in the root (and using Project app setting to point to the correct project folder/.csproj file) it still doesn't work. And you cannot set Project setting to an .sln file path - the build fails then:
|
Reported it first here, but that repo doesn't seem to attract much attention, so posting it here as well.
Trying to deploy a .NET 7 Isolated project from git sources using Deployment Center (App Service Build Service).
The build succeeds, the log says that all files were successfully created and copied.
But the function does not appear in the list of functions and cannot be triggered (the URL returns 404).
When downloading the app's contents, the downloaded ZIP-file doesn't contain the binaries, only an empty
host.json
file.Build logs:
Repro steps:
Note that it works fine for .NET 6 InProc (last time I checked).
Is there anything that can be configured to make it work?
The text was updated successfully, but these errors were encountered: