Webapp create with runtime aspnet|V4.7 fails
See original GitHub issueThis is autogenerated. Please review and update as needed.
Describe the bug
When creating a webapp with the --runtime arg and specifying “aspnet|V4.7”. The same command succeeds with “node|10.6”, or any of the node runtime values (and possibly others).
Command Name
az webapp create
Errors:
update_site_config() takes 2 positional arguments but 3 were given
Traceback (most recent call last):
Temp\pip-install-3pnsb50r\knack\knack\cli.py, ln 206, in invoke
azure\cli\core\commands\__init__.py, ln 608, in execute
azure\cli\core\commands\__init__.py, ln 666, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 657, in _run_job
azure\cli\command_modules\appservice\commands.py, ln 55, in _polish_bad_errors
azure\cli\core\commands\__init__.py, ln 636, in _run_job
azure\cli\core\commands\__init__.py, ln 306, in __call__
azure-cli-core\azure\cli\core\__init__.py, ln 493, in default_command_handler
azure\cli\command_modules\appservice\custom.py, ln 135, in create_webapp
TypeError: update_site_config() takes 2 positional arguments but 3 were given
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
-
Put any pre-requisite steps here… az group create… az appservice plan create…
-
az webapp create --name {} --plan {} --resource-group {} --subscription {} --% --runtime "aspnet|V4.7"
or
az --% webapp create --name {} --plan {} --resource-group {} --subscription {} --runtime "aspnet|V4.7"
Expected Behavior
I expect the web app to be created with .net 4.7 configured as the stack.
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
azure-cli 2.1.0
Extensions:
application-insights 0.1.3
interactive 0.4.3
storage-preview 0.2.10
Additional Context
After creating the app with node as the runtime, then navigating to the app thru the Azure portal the stack is listed as .net V4.7.
Tried PowerShell & Bash
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
az webapp create with runtime aspnet|v4.7 #12408 - GitHub
Describe the bug I am testing the following command az webapp create \ --resource-group $rg \ --name $APPSERVICE \ --plan ...
Read more >You need to ensure that WebApp1 uses the ASP.NET v4.7 ...
You plan deploy an Azure web app that will have the following settings: Name: WebApp1; Publish: Docker container; Operating system: Windows ...
Read more >Create a WebApp in App Service Environment - Ankit Sarkar
Runtime Stack : ASP.NET V4.7. Operating System : Windows. Region : intranet (Newly Created ASE). App Service Plan : I1 (sandbox-appservice).
Read more >How to Deploy Web Apps with Azure - Towards Data Science
Most of these options will be specific to what you are building — but for Runtime stack select ASP.NET V4.7 and of-course choose...
Read more >Common error troubleshooting for Azure App Service and IIS ...
Provides troubleshooting advice for the most common errors when hosting ASP.NET Core apps on Azure Apps Service and IIS.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is now working for me: az webapp create --name {} --plan {} --resource-group {} --subscription {} --% --runtime “aspnet|V4.7”
webapp was created successfully with the correct stack.
az version
{ “azure-cli”: “2.2.0”, “azure-cli-command-modules-nspkg”: “2.0.3”, “azure-cli-core”: “2.2.0”, “azure-cli-nspkg”: “3.0.4”, “azure-cli-telemetry”: “1.0.4”, “extensions”: { “application-insights”: “0.1.3”, “azure-devops”: “0.17.0”, “interactive”: “0.4.3”, “storage-preview”: “0.2.10” } }
PS F:\Repos\Offline\Auth-Hub> az version
This command is in preview. It may be changed/removed in a future release. { “azure-cli”: “2.2.0”, “azure-cli-command-modules-nspkg”: “2.0.3”, “azure-cli-core”: “2.2.0”, “azure-cli-nspkg”: “3.0.4”, “azure-cli-telemetry”: “1.0.4”, “extensions”: { “aks-preview”: “0.4.33”, “dev-spaces”: “1.0.3”, “front-door”: “1.0.2” } }
and still getting an error: ‘V4.7’ is not recognized as an internal or external command. web app not created.