Microsoft, the example of using the pom with azure-functions-maven-plugin creates weird obj/ and extensions.csproj files on my local machine when doing mvn package command.
And when executing in azure devops it fails because the func-core-tools cannot be downloaded. I wonder why Microsoft decided to combine the packaging function and the local:run and deploy functions into one plugin and demand I give the configuration to my resource-group, etc. I will deploy it myself with the AzureFunctionDeploy in Azure devops.
Why does Microsoft example pom here copy the local.settings.json in the function package? Isn't that a big horror move considering local secrets are kept in the local.settings.json?
Why does Microsoft think that it is cool to create an extensions.csproj file in my Java project when running mvn package? Am I the first person who tries to deploy an Azure java function using Azure devops? Are the rest of them still playing with hello world deployments?
Microsoft, please let me do the packaging of the function and without all the nice run-local and deploy functionality. Or at least let me know how to package without the azure-functions-maven-plugin and what to include in the package and I can do it myself. This example does not help.
Hi @sijucm !
I am a new open source contributor and would like to solve this issue, could you help me understand the issue better by providing some extra references ?
Is this is issue open to contribute ?
Microsoft, the example of using the pom with azure-functions-maven-plugin creates weird obj/ and extensions.csproj files on my local machine when doing mvn package command.
And when executing in azure devops it fails because the func-core-tools cannot be downloaded. I wonder why Microsoft decided to combine the packaging function and the local:run and deploy functions into one plugin and demand I give the configuration to my resource-group, etc. I will deploy it myself with the AzureFunctionDeploy in Azure devops.
Why does Microsoft example pom here copy the local.settings.json in the function package? Isn't that a big horror move considering local secrets are kept in the local.settings.json?
Why does Microsoft think that it is cool to create an extensions.csproj file in my Java project when running mvn package? Am I the first person who tries to deploy an Azure java function using Azure devops? Are the rest of them still playing with hello world deployments?
Microsoft, please let me do the packaging of the function and without all the nice run-local and deploy functionality. Or at least let me know how to package without the azure-functions-maven-plugin and what to include in the package and I can do it myself. This example does not help.