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

function app: az functionapp create should support slots creation #9126

Closed
exc3eed opened this issue Apr 17, 2019 · 12 comments
Closed

function app: az functionapp create should support slots creation #9126

exc3eed opened this issue Apr 17, 2019 · 12 comments
Assignees
Labels
Functions-cli H2-2019 Features to be finished by the second half of 2019 Service Attention This issue is responsible by Azure service team.

Comments

@exc3eed
Copy link

exc3eed commented Apr 17, 2019

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
Cannot create slot for Function app. Following error is returned.
"Function App app settings are not expected to be empty. Please try again with WEBSITE_CONTENTAZUREFILECONNECTIONSTRING as a storage account connection string"
To Reproduce
Just execute this command
az webapp deployment slot create --name <function_app_name>--resource-group deletete --slot <slot_name>
Expected behavior
Slot should be created successfully for function app.

Environment summary
Additional context
Add any other context about the problem here.

@panchagnula
Copy link
Contributor

@ankitkumarr this is the bug from the CRI - if you have an existing bug please link the bugs.

@panchagnula panchagnula added this to the Sprint 61 milestone Apr 19, 2019
@Chedberg84
Copy link

👍
I am also experiencing this issue.

I am using an Azure Function runtime version ~2. Following the Terraform example here: https://vgaltes.com/post/deploying-azure-functions-using-slots/

I was able to confirm I see the same issue as stated by @exc3eed above when running the az webapp deployment slot create command. Adding the storage account connection string doesn't seem to change the exception thrown:

Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="Function App app settings are not expected to be empty. Please try again with WEBSITE_CONTENTAZUREFILECONNECTIONSTRING as a storage account connection string.

@panchagnula
Copy link
Contributor

@Chedberg84 az webapp should not be used for functionapp - the az functionapp * commands should be used for functionapp & slots creation for functionapp is not currently supported.

@panchagnula panchagnula changed the title Unable to create Function app slot function app: az functionapp create should support slots creation Apr 23, 2019
@afuggetta
Copy link

Hello,

Is this on track to be deployed on May 15th?

Thanks

@ahmedelnably
Copy link
Contributor

We are still working on this, unfortunately the support for slots in the create command will not be out by May 15th

@ahmedelnably ahmedelnably removed this from the Sprint 61 milestone May 13, 2019
@bigdatamoore
Copy link

any idea when this will be available?

@ahmedelnably
Copy link
Contributor

We will start working in the near future, we still do not have a concrete ETA yet

@ankitkumarr
Copy link
Contributor

We have started the work #9550. It should be completed in Sprint 63 (Official Release: 6/18/2019).

@achandmsft achandmsft added the H2-2019 Features to be finished by the second half of 2019 label Jun 13, 2019
@bsiegel bsiegel added the Service Attention This issue is responsible by Azure service team. label Jun 14, 2019
@ankitkumarr
Copy link
Contributor

This can be closed @ahmedelnably. Work was completed and released.

@rerime
Copy link

rerime commented Jun 19, 2019

BUG!
az functionapp deployment slot create
It is clone all settings from main function. Including variable WEBSITE_CONTENTSHARE
So it leads to deploy to same function.
In Azure Portal it generate random WEBSITE_CONTENTSHARE variable based on function name.

@ahmedelnably
Copy link
Contributor

@rerime thanks for reporting the issue, we will be fixing that in the next release

@ahmedelnably
Copy link
Contributor

Thanks to @ankitkumarr the fix is addressed in #9731

@haroldrandom haroldrandom added Feature Functions-cli H2-2019 Features to be finished by the second half of 2019 Service Attention This issue is responsible by Azure service team. labels Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functions-cli H2-2019 Features to be finished by the second half of 2019 Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests