Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure function not reading the exsiting storage account values #30626

Closed
jamshaidishaque opened this issue May 6, 2019 · 4 comments
Closed

Comments

@jamshaidishaque
Copy link

jamshaidishaque commented May 6, 2019

Hi Team,

I am still facing the issue of not linking the existing storage account with Azure function.

Every time when I try to deploy a Azure function with maven mvn azure-functions:deploy 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>


Document Details

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

@PramodValavala-MSFT
Copy link
Member

@jamshaidishaque Unfortunately, I believe this isn't supported yet. As mentioned in #19298 where you've also commented, there is an open issue microsoft/azure-maven-plugins#110 for supporting this.

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>

We are assigning this issue to the content author for review and for updating the docs once this is supported.

@ggailey777
Copy link
Contributor

reassign:ggailey777

@ggailey777
Copy link
Contributor

unassign:rloutlaw

@ggailey777
Copy link
Contributor

I am not able to reproduce this issue any longer, so I assume it's been fixed. We do use a republish scenario in the new Java extended quickstart. Please reopen if still an issue. #please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants