I’ve been having some issues deploying an azure function app through GitHub actions, and it turns out the issue comes down to the zip file being made by the create-zip-package-action doesn’t include the directory .azurefunctions. If I swap this action out for a step that just calls Compress-Archive pwsh commandlet then the files are there and it works. My step looks like this:
- name: Zip function app
Is there a different string I should be using in the files parameter that will also include folders that start with .? I just want everything included, no exceptions.
Just to confirm I’m following exactly what the scenario is, are you saying that there is a folder: ./publish/MyFunctionApp/.azurefunctions and that folder and its contents arent getting packaged up using our built in step?
Hey Paul, thanks for the idea, but as written that file mask only picked up the top level folder of .azurefunctions. To pick up the contents of that folder and its sub folders I used the following file mask instead:
This will obviously only pick up folders starting with dots in the root directory, which is a little fragile, but this seems to work for me for now.
I should probably add some context here, in that the .azurefunctions folder isn’t one I’ve added (if it was I would have renamed it), it’s a standard folder that’s created by dotnet when building a isolated process azure function.