Function deploy creates the storage account

[abhinav-jain09]

HI Team,
when I deploy the function azure-functions:deploy it creates the storage account and as per my service plan it also create the storage service plan . Where are the setting to control it . it really frustrating that it creates the hell lot of stuff and no setting to control it.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e656bde5-b5d8-8d80-b7b3-ab430e57613e
• Version Independent ID: 329eb12f-7302-4ecf-c1bf-a50ba3f34bdf
• Content: Create your first function in Azure with Java and Maven
• Content Source: articles/azure-functions/functions-create-first-java-maven.md
• Service: azure-functions
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw, glenga

[KetanChawda-MSFT]

@abhinav-jain09 Thank you for your feedback! We will investigate and get back to you with our findings.

[PramodValavala-MSFT]

@abhinav-jain09 There are a few more configurations that the Functions Maven plugin can take. You can find more information here.

You can configure the App Service Plan to use by making these changes to your pom.xml

1. Add this to project > properties

<functionAppServicePlanName>WestUS2Plan</functionAppServicePlanName>

If you have an existing App Service Plan with a different name, change it here.

2. Add this to line under the configuration for the azure-functions-maven-plugin

<appServicePlanName>${functionAppServicePlanName}</appServicePlanName>

With these settings, it should use the existing App Service Plan with the same name mentioned.

Unfortunately, there is no way to configure the storage account details as of today.
This shouldn't be a very big problem since storage accounts are not recommended to be shared across multiple function apps.

[abhinav-jain09]

whatever function creates by default via portal it should be configurable by mvn otherwise no point of using maven because it cannot do the job completely. everytime I deoply the new function it create the new storage account with its own naming convention . we have internally our naming convention to define the resouce name.

[PramodValavala-MSFT]

@abhinav-jain09 This indeed is a valid scenario that you are trying to achieve.

Since Java for Azure Functions is still in Preview, there are still things that require ironing out.
It would be best to create a separate issue on this repo to address this issue accordingly.

[PramodValavala-MSFT]

@abhinav-jain09 I have referenced this in another issue in the functions maven plugin repo which discusses the same functionality requirement which is a better avenue to continue the discussion.

As there is no doc update required at this time, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

[jamshaidishaque]

I am still facing this issue, every time when I try to create a Azure function with maven it is not reading my connection-string from pom.xml and create a new storage account.

I am providing the value like this

<property>
<name>AzureWebJobsStorage</name>
<value>Storage_account_connection-string</value>
<property>

[PramodValavala-MSFT]

@abhinav-jain09 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>