Add FunctionApp "modules path" to PSModulePath about azure-functions-powershell-worker HOT 5 CLOSED

I believe PSDepend and Powershell 6.1 should be part of the powershell azure functions docker image. Here is a way to work with the example PSCoreApp and install dependencies:

# Install powershell project dependencies
FROM mcr.microsoft.com/powershell:6.1.0-debian-8 as builder

WORKDIR /tmp
COPY ./requirements.psd1 .
RUN pwsh -c "Install-Module -Name PSDepend -Scope CurrentUser -Force" \
    && pwsh -c "Set-Location . ; Invoke-PSDepend -Force"

FROM mcr.microsoft.com/azure-functions/powershell:2.0

WORKDIR $AzureWebJobsScriptRoot
COPY --from=builder /tmp/Modules/ /azure-functions-host/workers/powershell/Modules/
COPY . .

from azure-functions-powershell-worker.

So this would be to have the container do the installing of the Modules and allow the user to specify them in the requirements.psd1 rather than having to bundle their modules themselves?

from azure-functions-powershell-worker.

from azure-functions-powershell-worker.

As you guys can see in the python and Nodejs docker image, at least one package management is available (pip and npm, respectively). They are not doing the dependencies installation as far as I know, but makes everything easy to start if you have them available.
If none of this makes sense, do put a dockerfile in the example folder so that even people without powershell installed in their local machine can try it out.
About not being opinionated, the moment you chose to have the worker and the example using PSDepend that went out the window, don’t you think? Not that I mind because I think PSDepend is quite useful and simple to use.
Also, keep in mind that some of us like me and my company would be using the Azure Functions with container directly so it would be no pack before deploy.

from azure-functions-powershell-worker.

from azure-functions-powershell-worker.