Create more human-friendly names for associated services about azure-maven-plugins HOT 5 CLOSED

There was a similar request at MicrosoftDocs/azure-docs#19298 for which I found that there is a provision to use an existing App Service Plan by setting this configuration to the maven plugin as mentioned in the README

<appServicePlanName>${functionAppServicePlanName}</appServicePlanName>

assuming a property with the same name is defined in pom.xml

Currently, the code at this line creates a new app service plan if the above configuration is not set.
But if it is set, it tries to use an existing plan without really checking if it exists.

Unfortunately, looking at the Java SDK, the functions / appservice implementation doesn't allow for passing a name when creating the app service plan but is possible in general as evident from this code.

On the bright side, storage account does seem to be possible as available here for new storage accounts with name and also existing ones.

from azure-maven-plugins.

Yes, I agree that with standard naming scheme, user can easily guess it in advance. But it will also increase the posibility of creation failure because of the duplicated dns name. Could you please help describe more about the usage scenario?

@hexiaokai What do you think about this?

from azure-maven-plugins.

I thought there might be a concern about naming collisions. Is it possible for you to query if the name exists, and if it does create the service with a -1, -2, etc?

from azure-maven-plugins.

Emm, in the plugin code, we pass the app name to the Azure ava SDK to provision the resource:

https://github.com/Microsoft/azure-maven-plugins/blob/master/azure-functions-maven-plugin/src/main/java/com/microsoft/azure/maven/function/DeployMojo.java#L146

I'm not sure if it is possible to specify the appservice plan name now in the Azure Java SDK.

from azure-maven-plugins.

Here is a workaround for this until its officially supported

As a workaround, you could use the maven plugin just for building and then use func to deploy.

I assume you've already created a function app as documented in the Azure CLI Quickstart.

1. Build the app

mvn clean package

1. Use func to publish

# Change to the staging directory
cd target/azure-functions/<appName>
# Would be something like this - cd target/azure-functions/<artifactId>-20190506045816127

# Deploy using func
func azure functionapp <FunctionAppName>

from azure-maven-plugins.