text:
global configuration files created with aztk spark init --global are not found in other dirs

When I run:
aztk spark init --global
a .aztk/ directory is correctly created in my $HOME dir. I edit the secrets.yaml file to configure keys, account names etc. But when I try and create a cluster in another location using the command:
aztk spark cluster create --id spark --vm-size standard_a2 --size 4
I get the message:
Batch account key is not set in secrets.yaml config
The workaround is to copy the directory ./aztk/ in my $HOME dir to the location I'm trying to create the cluster. I'm using the latest release of aztk with python 3.6.2 on MacOS High Sierra 10.13.1
conda list gives:
azure-batch               3.0.0
azure-common          1.1.8
azure-nspkg              2.0.0
azure-storage           0.33.0

I believe the wrong file path was being used to read the global secrets file. Just put out a PR to fix it. Nice catch!

authors: jafreck willferreira

repo: Azure/aztk


text:
bump aks-preview to 0.5.35 for mig support

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

forgot to do this in #3895

aks-preview

source: gharchive/pull-request

authors: alexeldeib yonzhan

repo: Azure/azure-cli-extensions

license: MIT

license_type: permissive

license_source: github-api


text:
[ssh] Bug Fix: Change how ssh vm reads the ssh client logs

Fix: https://github.com/Azure/azure-cli-extensions/issues/4915#issuecomment-1243939019

ssh vm reads the logs from ssh client and ssh proxy to delete sensitive information when it is no longer needed and print helpful error messages for known errors. Our approach to do that was causing ssh banners to be printed after the ssh process was terminated, and not before authentication.
Known issue: we are no longer able to read ssh proxy error channel when the user is running the command from a linux machine to connect to a local user on an arc machine. That is not a breaking change, but users in this particular situation will not get a helpful error message if there is an error with the proxy.

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

ssh


text:
{AzureAppService} Fixing the supported api-version for get_kube_client() function

Fixes Azure/azure-cli-extensions#6155
We get the below error while running CLI command: az appservice kube show
Enviornment:
Windows-10-10.0.20348-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.47.0

Extensions:
appservice-kube 0.1.7

Error:
  File "C:\Users\Administrator\.azure\cliextensions\appservice-kube\azext_appservice_kube\custom.py", line 305, in show_kube_environments
    client = _get_kube_client(cmd)
  File "C:\Users\Administrator\.azure\cliextensions\appservice-kube\azext_appservice_kube\custom.py", line 301, in _get_kube_client
    return client.kube_environments
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/mgmt/web/_web_site_management_client.py", line 627, in kube_environments
ModuleNotFoundError: No module named 'azure.mgmt.web.v2021_01_01'

This error is because API version 2021-01-01 is trimmed from azure-mgmt-web SDK by scripts/trim_sdk.py to reduce MSI package size (#23946)
but appservice-kube extension hardcodes 2021-01-01:
https://github.com/Azure/azure-cli-extensions/blob/f4033ee2830c68668f340e12c39d76b6d2b7ee3f/src/appservice-kube/azext_appservice_kube/custom.py#L300
appservice-kube extension can use the latest API version api_version="2022-03-01" defined at:
https://github.com/Azure/azure-cli/blob/8c45b0feeaaa9a8ca3ed53c5cead1a8435b04fa6/src/azure-cli-core/azure/cli/core/profiles/_shared.py#L243

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AzureAppService

@StrawnSC Could you please review this once you get a chance ? Thanks in advance.

ERROR    cli.azure.cli.core.azclierror:azlogging.py:212 Can't overwrite existing cassette ('/mnt/vss/_work/1/s/src/appservice-kube/azext_appservice_kube/tests/latest/recordings/test_win_webapp_quick_create_runtime_kube.yaml') in your current record mode ('once').
No match for the request (<Request (GET) https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/clitest000001?api-version=2022-09-01>) was found.
Found 2 similar requests with 1 different matcher(s) :

1 - (<Request (GET) https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/clitest000001?api-version=2021-04-01>)..)
Matchers succeeded : ['method', 'scheme', 'host', 'port', 'path']
Matchers failed :
_custom_request_query_matcher - assertion failure :
None

The CI issues are caused by the bumping api-version of Resource RP from 2021-04-01 to 2022-09-01 in azure-cli-core, so you need to pull the latest code from the remote dev branch of Azure/azure-cli repo and then re-record these failed tests in live mode.

authors: navba-MSFT yonzhan zhoxing-ms


text:
Upgrade az vmware extension to use 2023-03-01 API version

az vmware: update to AVS 2023-03-01 API
az vmware private-cloud create: Add new --ext-nw-blocks parameter
az vmware private-cloud update: Add new --ext-nw-blocks parameter

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

Hi @jonathanhe-msft and @cataggar. I've changed the related the code. Could you help update the test recordings in your mock servers. Thanks.

az vmware placement-policy vm-host and az vmware placement-policy vm aren't working properly as they're missing a required affinityType parameter: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-03-01/vmware.json#L7718

az vmware hcx-enterprise-site-create failing due to bad request. the request looks fine to me, but the mock server isn't accepting the values. I think it's an error with the mock, but can you confirm everything looks ok from your end?

vmware private-cloud add-identity-source fails with ResourceNotFoundError, even though i see the calls made successfully to our mock server:

aren't working properly as they
jonathanhe-msft Could you use the --debug argument to check the api response. It seems the affinityType isn't returned in the api response of Get method. The update command will GET the resource first. And as affinityType is not exposed as an argument, the value will be inherent from the GET response. According to api specs, that property should be included in api response.

az vmware hcx-enterprise-site-create failing due to bad request. the request looks fine to me, but the mock server isn't accepting the values. I verified with the old implementation (pre-migration) and it is working as expected. can you take a look?

Fixed in this commit(https://github.com/Azure/azure-cli-extensions/pull/6765/commits/7d7faac452443a57c953f1806df6300074db8cd3)

vmware private-cloud add-identity-source fails with ResourceNotFoundError, even though i see the calls made successfully to our mock server:

That's because the

vmware private-cloud add-identity-source fails with ResourceNotFoundError, even though i see the calls made successfully to our mock server:

That's because the newly added identity source is missed in the response of your mock server. I also find this issue in old recordings and I manually fixed the server response in previous migration PR.

az vmware placement-policy vm-host and az vmware placement-policy vm aren't working properly as they're missing a required affinityType parameter: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-03-01/vmware.json#L7718

jonathanhe-msft Could you use the --debug argument to check the api response. It seems the affinityType isn't returned in the api response of Get method. The update command will GET the resource first. And as affinityType is not exposed as an argument, the value will be inherent from the GET response. According to api specs, that property should be included in api response.

confirmed get response is missing the affinityType property. working on fixing and will update live tests once complete.

@zhoxing-ms Please help review this PR.

authors: jonathanhe-msft kairu-ms yonzhan


text:
Update API for Aks Edge Essentials

This PR updates the get calls for annotations to provide distribution names for aks-edge-k3s and aks-edge-k8s.

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Draft

Please add test for this new feature.

Please add test for this new feature.

When you do kubectl get nodes on that infrastructure, you get an api response. In the infrastructure, the distro name is aks-edge-k3s. The test is dependent on the underlying infrastructure. We worked with the customer on validating this feature on that particular infrastructure. It passed the validation for the aks-edge-essentials scenario where this feature was tested on on-prem server with aks-edge-k3s/k8s configuration.

authors: 9lash yanzhudd yonzhan


text:
az webapp: Magic .azure files created in my development environment during deploy

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

Describe the bug
During the deployment two magic files were created in my development environment — .azure and .deployment. These files didn't have comments or links to any documentation regarding what these files were for, what they contained, or if the options were configurable
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
Add any other context about the problem here.

Running az webapp up configures local context for which is included in the .Azure files see https://docs.microsoft.com/en-us/cli/azure/reference-index?view=azure-cli-latest#az-configure for more details.
Adding @btardif  as FYI.

We should add a comment to the content of the files with links to more info or explanation of what they are and what they are used for... re-opening this and assigning to me to come up with plan

move to S166.

@btardif any update for this issue?

move to S167

@yonzhan , @btardif and I just had a quick chat about this issue and the webapp team is suspecting that the magical .azure file is being created via the CLI rather than the az webapp up command. There's confusion on what this file is and how to make use of it. It'd be great if we could investigate and confirm on what's happening and the next steps

@Juliehzl please help to investigate the issue mentioned above.

move to S169

@chenlomis this is the same issue being discussed here: https://dev.azure.com/azuretracking/Azure tracking/_workitems/edit/680

add to S173

.azure should be a folder instead of a file, created by Azure CLI as the configuration folder.
https://github.com/Azure/azure-cli/blob/3b4d10d473a8d72dc2a1607478beb14424ce2004/src/azure-cli-core/azure/cli/core/_environment.py#L12
It is by-default created under the user's home folder, unless

AZURE_EXTENSION_DIR is set
az configure --scope local is used
local-context is turn on

.deployment seems to be created by botservice:
https://github.com/Azure/azure-cli/blob/9370ec21d5febcb0e7099f1a3969a42d04c4ceb1/src/azure-cli/azure/cli/command_modules/botservice/custom.py#L560
Please share the full deployment script for us to further analyze the issue.

The deployment path used is here:
https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-python?tabs=bash
This generates a .azure/config file with no comment explaining what it is for.
The .deployment file comes from VS Code deploy so that is a separate issue.

We have a document Azure CLI configuration explaining what .azure/config is.
Indeed, we can put a comments in .azure/config explaining what it is. @yonzhan @achandmsft @chenlomis, any thoughts?

Sounds like a plan to me
Something along the lines of:" this is where your CLI configs are stored"
@qubitron that aligns with your proposal right?

Yep something like "This file contains saved configurations for your CLI, read more at: aka.ms/1234".
We probably want an aka link in case we change where this points to.

@jiasli @chenlomis should we re-open the issue?

Created issue https://github.com/Azure/azure-cli/issues/15001 to track.

source: gharchive/issue

authors: btardif chenlomis jiasli panchagnula qubitron yonzhan

repo: Azure/azure-cli


text:
Very ugly error message when using az account logging update command on a Storage Account of kind BlobStorage or sku.tier Premium

If you try to exeute az account logging update with a Premium storage account or with a BlobStorage storage account, you will get an error similar to the following:
az>> az storage logging show --account-name xxxxxxxxxxx --subscription xx-xxx-xxx
The command failed with an unexpected error. Here is the traceback:
HTTPSConnectionPool(host='xxxxxxxxxx.queue.core.windows.net', port=443): Max retries exceeded with url: /?restype=service&comp=properties (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x00DFC830>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',))
Traceback (most recent call last):
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connection.py", line 159, in _new_conn
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\util\connection.py", line 57, in create_connection
File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\socket.py", line 745, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno 11002] getaddrinfo failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connectionpool.py", line 600, in urlopen
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connectionpool.py", line 343, in _make_request
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connectionpool.py", line 839, in _validate_conn
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connection.py", line 301, in connect
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connection.py", line 168, in _new_conn
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x00DFC830>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\requests\requests\adapters.py", line 449, in send
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\connectionpool.py", line 638, in urlopen
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-hb486cm7\urllib3\urllib3\util\retry.py", line 399, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='xxxxxxxxxxx.queue.core.windows.net', port=443): Max retries exceeded with url: /?restype=service&comp=properties (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x00DFC830>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\storageclient.py", line 321, in _perform_request
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common_http\httpclient.py", line 92, in perform_request
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\requests\requests\sessions.py", line 533, in request
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\requests\requests\sessions.py", line 646, in send
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\requests\requests\adapters.py", line 516, in send
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='xxxxxxxxx.queue.core.windows.net', port=443): Max retries exceeded with url: /?restype=service&comp=properties (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x00DFC830>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\bhulse.azure\cliextensions\interactive\azext_interactive\azclishell\app.py", line 662, in cli_execute
result = invocation.execute(args)
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core\commands_init_.py", line 603, in execute
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core\commands_init_.py", line 661, in run_jobs_serially
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core\commands_init.py", line 652, in run_job
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core\commands\arm.py", line 750, in show_exception_handler
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core\commands_init.py", line 631, in run_job
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core\commands_init.py", line 306, in call
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli-core\azure\cli\core_init_.py", line 485, in default_command_handler
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli\azure\cli\command_modules\storage\operations\logging.py", line 15, in get_logging
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-cli\azure\cli\command_modules\storage\services_wrapper.py", line 29, in get_logging
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\queue\queueservice.py", line 372, in get_queue_service_properties
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\storageclient.py", line 430, in _perform_request
File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-umfcm_n2\azure-multiapi-storage\azure\multiapi\storage\v2018_11_09\common\storageclient.py", line 361, in _perform_request
azure.common.AzureException: HTTPSConnectionPool(host='xxxxxxxxxxx.queue.core.windows.net', port=443): Max retries exceeded with url: /?restype=service&comp=properties (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x00DFC830>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',))
I would have expected a simple error message along the lines of:
Premium Storage accounts do not support logging
BlobStorage storage accounts do not support logging.
I though I was having a problem with api quotas.

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

ID: c237378a-a708-8e2f-3c8c-0bc8b623d21c
Version Independent ID: c4e27b67-9605-60f5-899d-8ffd727079b2
Content: az storage logging
Content Source: src/azure-cli/azure/cli/command_modules/storage/_help.py
Service: storage
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S168

Hi @hulseware,  sorry for late response first.
There are several points to clarify here:

Are you using az interactive to run cli commands?
When I try to reproduce your issue with normal cli (not in interactive mode), I only get one exception not four exceptions like what in your scenario. Here is what I get:

HTTPSConnectionPool(host='zuhblob.queue.core.windows.net', port=443): Max retries exceeded with url: /?restype=service&comp=properties (Caused by NewConnectionError('<urllib3.connection.HTTPSConnect
ion object at 0x000001F15CE28288>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

Your suggestion is very valuable to us. As you mentioned, the error occurs because of specific storage account type. Actually it is caused by default value (bqt) in --services parameter:

BlobStorage doesn't support logging for queue service;
PremiumStorage doesn't support logging for blob/queue/table services.
I will refine the error message to make it point to wrong storage account type.

Yes, I use az interactive while developing the right cli commands to add to utilities targeted at maintaining better security across the subscriptions I am managing for my team. So the extra tracebacks were coming from the az interactive tool.
Yes, I believe that message is what I see when running via the normal command line.

Thanks for working to make the error message more descriptive of the real problem!
From: Zunli Hu notifications@github.com
Sent: Thursday, May 21, 2020 2:11 AM
To: Azure/azure-cli azure-cli@noreply.github.com
Cc: Hulse, Bruce bhulse@ptc.com; Mention mention@noreply.github.com
Subject: Re: [Azure/azure-cli] Very ugly error message when using az account logging update command on a Storage Account of kind BlobStorage or sku.tier Premium (#11969)
External email from: noreply@github.commailto:noreply@github.com
Hi @hulsewarehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhulseware&data=02|01|bhulse%40ptc.com|f25ae0dc795942b8432f08d7fd4dd671|b9921086ff774d0d828acb3381f678e2|0|0|637256383063474220&sdata=Zo%2FTrRWewqd33HZtjCS%2FtKAUGF%2FCs%2F2qoIMW0OlqI28%3D&reserved=0, sorry for late response first.
There are several points to clarify here:

Are you using az interactive to run cli commands?
When I try to reproduce your issue with normal cli (not in interactive mode), I only get one exception not four exceptions like what in your scenario. Here is what I get:

HTTPSConnectionPool(host='zuhblob.queue.core.windows.net', port=443): Max retries exceeded with url: /?restype=service&comp=properties (Caused by NewConnectionError('<urllib3.connection.HTTPSConnect
ion object at 0x000001F15CE28288>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

Your suggestion is very valuable to us. As you mentioned, the error occurs because of specific storage account type. Actually it is caused by default value (bqt) in --services parameter:

BlobStorage doesn't support logging for queue service;
PremiumStorage doesn't support logging for blob/queue/table services.
I will refine the error message to make it point to wrong storage account type.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F11969%23issuecomment-631902964&data=02|01|bhulse%40ptc.com|f25ae0dc795942b8432f08d7fd4dd671|b9921086ff774d0d828acb3381f678e2|0|0|637256383063479216&sdata=HCtaDxvR6agdww5TSxgEOE6WmNgJ4eTYKG3mk9%2Bpw00%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACLZFQQTT6JLU27D6HU6GFLRSTAYXANCNFSM4KM3LHYQ&data=02|01|bhulse%40ptc.com|f25ae0dc795942b8432f08d7fd4dd671|b9921086ff774d0d828acb3381f678e2|0|0|637256383063484198&sdata=Dj9dgmYAByp4XMcbQz9VIO6FfXbVtopi33iJZVX1u9A%3D&reserved=0.

authors: Juliehzl hulseware yonzhan


text:
az cli fails with ModuleNotFoundError

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp create
Errors:
No module named 'decorator'
Traceback (most recent call last):
python3/dist-packages/fabric/connection.py, ln 5, in <module>
    from invoke.vendor.six import StringIO
ModuleNotFoundError: No module named 'invoke.vendor.six'

...

python3/dist-packages/fabric/connection.py, ln 10, in <module>
    from decorator import decorator
ModuleNotFoundError: No module named 'decorator'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Install Ubuntu 20.4 LTS on Windows WSL
Install az cli following these steps: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view=azure-cli-latest#set-release
az login
az webapp create --name --resource-group --plan --runtime {}

Expected Behavior
az commands work
Environment Summary
Linux-4.4.0-18362-Microsoft-x86_64-with-glibc2.29
Python 3.8.2
Shell: bash

azure-cli 2.0.81

Extensions:
azure-devops 0.17.0

Additional Context

webapp

No related to app service - see https://github.com/Azure/azure-cli/issues/13644

I read all that at the time, I still couldn’t make it work on a fresh install following all the instructions. Care to elaborate? Someone else’s job?

@fengzhou-msft could you help with this?

@cuzzlor you need to first remove the packages installed by the old 2.0.81 azure-cli that comes with the Ubuntu 20.4 LTS. Try sudo apt remove azure-cli and make sure /usr/lib/python3/dist-packages/azure is deleted.

Ok. At the time it was a brand new install of WSL and the azure cli install script. I’ll try again maybe something has changed. Thanks.

You may need to run sudo apt autoremove after sudo apt remove azure-cli to remove the old azure packages that azure-cli 2.0.81 depends on.

Duplicate with #14011

authors: cuzzlor fengzhou-msft panchagnula yonzhan


text:
How to pass an argument parameter without defining a value?

I am trying to achieve three scenarios for a command. Is there a way to do this ?

az postgres server create                                        (no argument parameter passed)
az postgres server create --public-access               (no value passed for argument parameter --public-access)
az postgres server create --public access  ( a valid value is passed to argument parameter --public-access).

Is there a way to do (2) that is pass a parameter without a value ? I am running into the below error :
az postgres server create: error: argument --public-access: expected one argument.
If this is do-able, how should I differentiate between (1) and (2) that is whether the parameter is completely missing or is present with a missing value ?

postgres

@arde0708 what are the sample values of --public-access? What is the behavior for 2?
We have get_three_state_flag arg_type that can achieve 2 and 3, but it only support boolean values.

We would want to define three kind of values for --public-access

No value. Just the parameter is passed. Ex : 'az postgres flexible-server create --public-access' ( Adds neither a Vnet, nor a firewall rule)
Single IP. Ex :  'az postgres flexible-server create --public-access 10.23.202.44' (Behavior : Adds single firewall rule)
Multiple IP. Ex :  'az postgres flexible-server create --public-access 10.23.202.44-10.23.202.48' (Behavior : Adds range of firewall rules)
Don't pass the parameter itself 'Ex : az postgres flexible-server create' (Behavior : Adds Vnet, Subnet)

@yonzhan Single Server is being retired. We won't be fixing this at this point in time. Please, close this issue. Thanks!

authors: arde0708 fengzhou-msft nachoalonsoportillo yonzhan


text:
[Stream Analytics] Bugs related to clusterid property

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

Related command
az stream-analytics job update
In our streaming job definition, we have the following nested cluster and id properties:
"properties": {
"cluster": {
"id": "subscriptions/{mysub}/resourceGroup/{myrg}/etc..."
}
}

Describe the bug

In the CLI, this cluster id property gets translated into just id:
o	az stream-analytics job update --job-name 'asa-fleide-large396' --resource-group $rg --id $clusterId
We think this is a possible source of confusion for the user -- because this command is an operation on the job, it's reasonable to infer that id is the job id, not the cluster id. Could we possible change this parameter to clusterid?

Another possible scenario is that the user should be able to set this id value to null. I tried to do this via CLI (setting the value to null or empty string), but got the following error:

(LinkedInvalidPropertyId) Property id '' at path 'properties.cluster.id' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'.
Code: LinkedInvalidPropertyId
Message: Property id '' at path 'properties.cluster.id' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'.

Is there another way to set it this property to null? If not, can we remove this validation?
To Reproduce

az stream-analytics job update --job-name 'asa-fleide-large396' --resource-group $rg --id $clusterId
az stream-analytics job update --job-name 'asa-fleide-large396' --resource-group $rg --id ""

Expected behavior

property name is clusterid instead of id
user able to set id value to null

Environment summary

Additional context

route to CXP team

Noncustomer-reported issue. Adding Service team to look in this.

authors: navba-MSFT roslynlu yonzhan


text:
az webapp up does re-create existing appservice pan and does not upload published .net app

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

Related command

az webapp up -n $app -g $grp -p $plan --sku F1 -l $loc -r "DOTNET|6.0"
Describe the bug

Azure cli 2.45.0 az webapp up does re-create existing appservice pan insted of using it and does not upload published .net app - instead the raw source files are uploaded
To Reproduce

env=$RANDOM
grp=appservices-$env
loc=westeurope
plan=appservices-$env
app=cli-api-$env
az group create -n $grp -l $loc
az appservice plan create -n $plan -g $grp --sku S1
az webapp create -n $app -g $grp --plan $plan --runtime "DOTNET|6.0"
dotnet new webapi -n cli-api --framework net6.0
cd cli-api
az webapp up -n $app -g $grp -p $plan --sku F1 -l $loc -r "DOTNET|6.0"
cd ..
Expected behavior

the existing app service plan should be used and the app that has been processed by dotnet publish should have been uploaded
Environment summary

Windows 11, WSL, Azure cli 2.45.0
Additional context

route to CXP team

Adding Service team to look into this.

Unable to repro. Closing for now as this has been open for a while with no recent activity. Please update to the latest CLI version and let us know if this is still an issue.
Also, when running az webapp up after already creating the app using az webapp create, you don't need to specify the runtime/location/SKU again in az webapp up. The cli output when running the command might say "Creating AppServicePlan..." even though it already exists. We are aware of that bug and are addressing that separately. See https://github.com/Azure/azure-cli/issues/22767 for more details on that issue.

authors: arambazamba navba-MSFT seligj95 yonzhan


text:
Implement slot parameter for az functionapp function show

Related command

az functionapp function show
Is your feature request related to a problem? Please describe.

I can't find a way to run az functionapp function show and target a deployment slot (besides the default/production one).
It apparently does not offer a --slot parameter: https://learn.microsoft.com/en-us/cli/azure/functionapp/function?view=azure-cli-latest#az-functionapp-function-show

Describe the solution you'd like

Please consider adding a --slot parameter to az functionapp function show
Describe alternatives you've considered

I tried a workaround via modifying --name to match the test slots name, but that does not seem to work

Additional context

This is the context in which I would use the new parameter: https://github.com/luis261/aztraphile/blob/reintroduce-slot-bound-http-invocations/utils/aztra-utils.ps1#L334

Thank you for opening this issue, we will look into it.

Hello @luis261 Thank you for your feedback. This is a feature request I just added to our backlog. In the meantime, you would just have to make direct API calls to https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Web/sites/<functionAppName>/slots/<slotName>/functions/<functionName>?api-version=2022-03-01.

Hi @kamperiadis - glad to know it made the backlog! Thanks for keeping me in the loop. Also good to know the alternative via the direct API call (:

authors: kamperiadis luis261 yonzhan


text:
Add a VM to an AvailabilitySet after creation.

Description
Is there an azure-cli equivalent of this powershell cmdlet? Described here:
https://www.petri.com/understanding-azure-availability-sets
https://docs.microsoft.com/en-us/powershell/module/azure/set-azureavailabilityset?view=azuresmps-4.0.0`
The first link has an example like this:
Get-AzureVM -ServiceName contosodc1 -Name contosodc1 | Set-AzureAvailabilitySet -AvailabilitySetName contosodcs | Update-AzureVM

Environment summary
Install Method: nightly
CLI Version: azure-cli (2.0.12+1.dev20170808)
OS Version: ubuntu 16.04 x64
Shell Type: bash

Hi @nneul there is no dedicated command for this. I tried to accomplish this via generic update and had no luck.  It seems you must specify the availability set when you create the VM (at least currently in 2.0)  We have an open project to improve the adding of VMs to load balancers and application gateway pools.
I'll investigate some potential solutions for this next sprint and see if we can get something into the next release. Ideas would be having an availability-set add-vm command, or adding availability set as strongly typed parameter on vm update.

Moving this into the same project as improving LB/AG experience.

Anything new here?

The item is on our backlog but not planned for upcoming work.  @yugangw-msft does this fit into your upcoming sprint plans?

@tjprescott, I will take a look in the next sprint

I have confirmed with Compute team that adding an existing VM to an existing av-set only works with RDFE(cloud service). For Compute RP, the only time you can add to an av-set is during VM create.

authors: nneul superminiek tjprescott yugangw-msft


text:
az webapp deployment source config-zip fails from jenkins pipeline

Describe the bug
We are using Jenkins integration with Azure. While trying to run az deploy webapp from jenkins pipeline it fails with the following error:
az webapp deployment source config-zip --debug --resource-group st-worker-test --name st-worker-test --slot stagedeploy --src /var/lib/jenkins/workspace/tore-backend-latest_develop@2/artifact/App.Store.Work_develop_549.zip
ERROR: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 197, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 369, in execute
six.reraise(*sys.exc_info())
File "/opt/az/lib/python3.6/site-packages/six.py", line 693, in reraise
raise value
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 343, in execute
result = cmd(params)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 182, in call
return self.handler(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/init.py", line 436, in default_command_handler
result = op(**command_args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 188, in enable_zip_deploy
response = response.json()
File "/opt/az/lib/python3.6/site-packages/requests/models.py", line 896, in json
return complexjson.loads(self.text, **kwargs)
File "/opt/az/lib/python3.6/json/init.py", line 354, in loads
return _default_decoder.decode(s)
File "/opt/az/lib/python3.6/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/opt/az/lib/python3.6/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
To Reproduce
Set to Azure serviceprincipal credentials
use Azure cli commands for the below:
login to Azure with service principal
set to the azure subscription
run az webapp deployment source config-zip --debug --resource-group st-worker-test --name st-worker-test --slot stagedeploy --src /var/lib/jenkins/workspace/tore-backend-latest_develop@2/artifact/App.Store.Work_develop_549.zip
The command above fails with the error mentioned.
Expected behavior
It should deploy the zip file to Azure webapp sucessfully
Environment summary
Install Method  : sudo apt-get / CLI version (azure-cli (2.0.45)) / Ubuntu 16.0.4 / Shell Type  (bash)
Additional context
If i run the same command manually by logging in to the Jenkins slave it works successfully. We need to get this working from Jenkins pipeline and need help in fixing the issue.

Also seeing that the deployment hangs sometimes. Attached is the debug log. I really need help on this. Could someone please look into it.
azure-deploy-log.docx

@panchagnula

@panchagnula I think the right fix here is to make the timeout configurable with an optional flag. The current behavior is to be assumed as the default if no timeout is provided.

Same here using on a bash terminal under macos v10.14.1. When deploying the demo project under https://docs.microsoft.com/en-us/learn/modules/store-app-data-with-azure-blob-storage/7-blob-uploads-and-downloads it fails with a highly similar error:
az webapp deployment source config-zip --resource-group ${AZ_RES_GROUP} --name ${AZ_WEBAPP_NAME} --src ../site.zip

Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/knack/cli.py", line 197, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 369, in execute
    six.reraise(*sys.exc_info())
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/six.py", line 693, in reraise
    raise value
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 343, in execute
    result = cmd(params)
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 182, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/azure/cli/core/__init__.py", line 436, in default_command_handler
    result = op(**command_args)
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/azure/cli/command_modules/appservice/custom.py", line 262, in enable_zip_deploy
    response = response.json()
  File "/usr/local/Cellar/azure-cli/2.0.48/libexec/lib/python3.7/site-packages/requests/models.py", line 892, in json
    return complexjson.loads(self.text, **kwargs)
  File "/Users/brandl/anaconda3/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/Users/brandl/anaconda3/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/Users/brandl/anaconda3/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

My zip file seems legit, and my CLI version is azure-cli (2.0.48)

@holgerbrandl  - what is the python version  that is being used here? is it possible for you to upgrade the python version & try? Do Ptyhon --version, this is the version i have installed "Python 3.7.0". thank you.

Since I had deleted the corresponding resource group already, I've created the complete demo setup again (group, storage account, wegapp) and tried to reproduce the error. However now it seems fine and deployment works as expected.
I'm not aware of any changes in my local setup. My python version has not changed since I have reported the ticket and is 3.6.3.
Not sure if this is compatible with the stacktrace, but it may have been also  some kind of connection timeout?

@holgerbrandl , thanks for the update. with the new setup has the version of azure-cli changed, especially since we have a newer version available now & we have had some code changes to the zip deployment command, so there might be some  bugfixes that would have infact fixed the problem you are seeing.

authors: holgerbrandl mattchenderson panchagnula swm7 tjprescott


text:
[Core] PREVIEW: Support Web Account Manager (WAM) login on Windows

Related command
az login
Description
Close #21201
Require https://github.com/AzureAD/microsoft-authentication-library-for-python/pull/415
Rework https://github.com/Azure/azure-cli/pull/22774
Testing Guide
On Windows, users can opt in WAM login using:
az config set core.allow_broker=true

Then run
az login

Instead of launching a web browser, an account selector will be shown to ask the user to select a Windows account:

History Notes

[Core] PREVIEW: Support Web Account Manager (WAM) login on Windows. To opt in, run az config set core.allow_broker=true
Additional information
WAM will be enabled by default in year 2023.

WAM support

authors: jiasli yonzhan


text:
Add profile switching params and profile listing command

Modify ‘az cloud register’ and ‘az cloud update’ to include the ‘—profile’ parameter
Add ability to view all supported API versions without querying a cloud

note: With this change, switching profile will not change anything as they are just example profiles.
FYI @lmazuel For the _shared.py file change. This would contain the resource type to api version map.
Closes https://github.com/Azure/azure-cli/issues/2280

Codecov Report

Merging #2398 into api-profile-support will increase coverage by <.01%.
The diff coverage is 77.14%.

@@                   Coverage Diff                   @@
##           api-profile-support    #2398      +/-   ##
=======================================================
+ Coverage                72.33%   72.33%   +<.01%
=======================================================
  Files                      323      325       +2
  Lines                    18273    18304      +31
  Branches                  2701     2707       +6
=======================================================
+ Hits                     13217    13240      +23
- Misses                    4223     4231       +8
  Partials                   833      833

Impacted Files
Coverage Δ

...cli-cloud/azure/cli/command_modules/cloud/_help.py
100% <100%> (ø)
:white_check_mark:

src/azure-cli-core/azure/cli/core/cloud.py
69.08% <100%> (+2.58%)
:white_check_mark:

...-cloud/azure/cli/command_modules/cloud/commands.py
100% <100%> (ø)
:white_check_mark:

...azure-cli-core/azure/cli/core/profiles/init.py
100% <100%> (ø)

...i-cloud/azure/cli/command_modules/cloud/_params.py
93.33% <100%> (+1.02%)
:white_check_mark:

src/azure-cli-core/azure/cli/core/_profile.py
83.78% <100%> (-0.15%)
:x:

.../azure-cli-core/azure/cli/core/profiles/_shared.py
100% <100%> (ø)

...li-cloud/azure/cli/command_modules/cloud/custom.py
17.24% <11.11%> (-1.13%)
:x:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c0fdcf...52e3356. Read the comment docs.

authors: codecov-io derekbekoe


text:
{Style} Use light theme by default on MacOS

Issue
We specify the color for warnings as ANSI color Bright Yellow without any specification of the actual RGB value:
https://github.com/Azure/azure-cli/blob/8d8d71707d6c60083d008062667cab18d0adaa25/src/azure-cli-core/azure/cli/core/style.py#L73
According to https://github.com/Azure/azure-cli/issues/18298#issuecomment-1263529261, MacOS's terminal by default uses white background and Bright Yellow is not readable on that white background.
Something like:

Personally, I think it should the terminal's theme's responsibility to make all ANSI colors readable on its background.
Change
Since MacOS's terminal by default uses white background, we by default uses light theme which uses (dark) Yellow for warnings:
https://github.com/Azure/azure-cli/blob/8d8d71707d6c60083d008062667cab18d0adaa25/src/azure-cli-core/azure/cli/core/style.py#L85
Cons
However, a disadvantage is that if the user manually chooses a dark background, or use an IDE like PyCharm with dark theme. There may be other readability issues if we default to light theme, such as blue, magenta.
As there isn't a way to detect the background color, there is no optimal solution. Users still need to run az config set core.theme=light/dark to select the color theme or totally disable color with az config set core.no_color=true.

https://stackoverflow.com/questions/58186391/text-displaying-as-bright-yellow-in-terminal
This is the interface for configuring ANSI color's real rendered RGB:


text:
Failed to create File Store directory Error:mkdir : The system cannot find the path specified.

Running the new azure-vnet-plugin.exe 1.0.3 on my Windows 10 Azure VM gives me the below error...
C:\temp\azure-vnet-cnm-windows-amd64-v1.0.3>azure-vnet-plugin.exe
Failed to create File Store directory Error:mkdir : The system cannot find the path specified.

Also, am I supposed to set the --api-url argument? What value should go there?
Thanks,
J-F

Closing as this is now fixed in latest release.

authors: frenchyjef sharmasushant

repo: Azure/azure-container-networking


text:
Update resource-group-move-resources.md

Added Express Route as not support moving a resource

Hi @andyjballgit, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@ggailey777 - I have double-checked this change. This pull request in azure-content can be merged.

Thanks for helping out with the Azure docs

authors: andyjballgit azurecla ggailey777 tfitzmac

repo: Azure/azure-content


text:
fixed minor typo

fixed minor typo

Hi @victorar, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (victorar). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@victorar : Thanks for your contribution to the Azure documentation! The author, @telmosampaio, has been notified to review your proposed change.

@telmosampaio
Easy typo. I'm accepting this PR. Thanks!
--Carolyn

@victorar
Nice catch! I'll accept this PR. Thank you!
--Carolyn

authors: PRmerger azurecla cjgronlund victorar


text:
Add pid to debug attach printout

Add pid to debug attach printout. Since attaching debugger to the process requires the PID, having it displayed saves an extra step and avoids confusion when multiple instances of azd is running.

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329 --version '' --verbose

pwsh:
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329' -Version '' -Verbose

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329' -Version '' -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/azd-windows-amd64.zip

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1329/azd-windows-amd64.msi

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-1329

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI Preview reference
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: puichan
ms.author: puichan
ms.date: 01/07/23
ms.topic: conceptual
ms.custom: devx-track-azdevcli
ms.prod: azure
Azure Developer CLI Preview reference
This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
azd
Azure Developer CLI is a command-line interface for developers who build Azure solutions.
Synopsis
Azure Developer CLI is a command-line interface for developers who build Azure solutions.
To begin working with Azure Developer CLI, run the azd up command by supplying a sample template in an empty directory:
	azd up –-template todo-nodejs-mongo

You can pick a template by running azd template listand then supplying the repo name as a value to --template.
The most common next commands are:
	azd pipeline config
	azd deploy
	azd monitor --overview

For more information, visit the Azure Developer CLI Dev Hub: https://aka.ms/azure-dev/devhub.
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage Azure Developer CLI configuration
azd deploy: Deploy the application's code to Azure.
azd down: Delete Azure resources for an application.
azd env: Manage environments.
azd infra: Manage Azure resources.
azd init: Initialize a new application.
azd login: Log in to Azure.
azd logout: Log out of Azure
azd monitor: Monitor a deployed application.
azd pipeline: Manage GitHub Actions pipelines.
azd provision: Provision the Azure resources for an application.
azd restore: Restore application dependencies.
azd template: Manage templates.
azd up: Initialize application, provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd config
Manage Azure Developer CLI configuration
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
The default value of the config directory is:

$HOME/.azd on Linux and MacOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
Options
  -h, --help   Gets help for config.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config get: Gets a configuration
azd config list: Lists all configuration values
azd config reset: Resets configuration to default
azd config set: Sets a configuration
azd config unset: Unsets a configuration
Back to top

azd config get
Gets a configuration
Synopsis
Gets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and MacOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config get <path> [flags]

Options
  -h, --help            Gets help for get.
  -o, --output string   The output format (the supported formats are json). (default "json")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage Azure Developer CLI configuration
Back to top

azd config list
Lists all configuration values
Synopsis
Lists all configuration values in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and MacOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config list [flags]

Options
  -h, --help            Gets help for list.
  -o, --output string   The output format (the supported formats are json). (default "json")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage Azure Developer CLI configuration
Back to top

azd config reset
Resets configuration to default
Synopsis
Resets all configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and MacOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.
azd config reset [flags]

Options
  -h, --help   Gets help for reset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage Azure Developer CLI configuration
Back to top

azd config set
Sets a configuration
Synopsis
Sets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and MacOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config set <path> <value> [flags]

Examples
azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options
  -h, --help   Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage Azure Developer CLI configuration
Back to top

azd config unset
Unsets a configuration
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and MacOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config unset <path> [flags]

Examples
azd config unset defaults.location

Options
  -h, --help   Gets help for unset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage Azure Developer CLI configuration
Back to top

azd deploy
Deploy the application's code to Azure.
Synopsis
Deploy the application's code to Azure.
When no --service value is specified, all services in the azure.yaml file (found in the root of your project) are deployed.
Examples:
	azd deploy
	azd deploy --service api
	azd deploy --service web

After the deployment is complete, the endpoint is printed. To start the service, select the endpoint or paste it in a browser.
azd deploy [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for deploy.
  -o, --output string        The output format (the supported formats are json, none). (default "none")
      --service string       Deploys a specific service (when the string is unspecified, all services that are listed in the azure.yaml file are deployed).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd down
Delete Azure resources for an application.
azd down [flags]

Options
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
  -o, --output string        The output format (the supported formats are json, none). (default "none")
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd env
Manage environments.
Synopsis
Manage environments.
With this command group, you can create a new environment or get, set, and list your application environments. An application can have multiple environments (for example, dev, test, prod), each with a different configuration (that is, connectivity information) for accessing Azure resources.
You can find all environment configurations under the .azure<environment-name> folder. The environment name is stored as the AZURE_ENV_NAME environment variable in the .azure<environment-name>\folder.env file.
Options
  -h, --help   Gets help for env.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env get-values: Get all environment values.
azd env list: List environments
azd env new: Create a new environment.
azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
azd env select: Set the default environment.
azd env set: Set a value in the environment.
Back to top

azd env get-values
Get all environment values.
azd env get-values [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.
  -o, --output string        The output format (the supported formats are json, dotenv). (default "dotenv")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env list
List environments
azd env list [flags]

Options
  -h, --help            Gets help for list.
  -o, --output string   The output format (the supported formats are json, table). (default "table")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env new
Create a new environment.
azd env new <environment> [flags]

Options
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env refresh
Refresh environment settings by using information from a previous infrastructure provision.
azd env refresh [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
  -o, --output string        The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env select
Set the default environment.
azd env select <environment> [flags]

Options
  -h, --help   Gets help for select.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env set
Set a value in the environment.
azd env set <key> <value> [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd infra
Manage Azure resources.
Options
  -h, --help   Gets help for infra.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd infra create: Create Azure resources for an application.
azd infra delete: Delete Azure resources for an application.
Back to top

azd infra create
Create Azure resources for an application.
azd infra create [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for create.
      --no-progress          Suppresses progress information.
  -o, --output string        The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd infra: Manage Azure resources.
Back to top

azd infra delete
Delete Azure resources for an application.
azd infra delete [flags]

Options
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for delete.
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd infra: Manage Azure resources.
Back to top

azd init
Initialize a new application.
Synopsis
Initialize a new application.
When no template is supplied, you can optionally select an Azure Developer CLI template for cloning. Otherwise, azd init initializes the current directory and creates resources so that your project is compatible with Azure Developer CLI.
When a template is provided, the sample code is cloned to the current directory.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd login
Log in to Azure.
Synopsis
Log in to Azure.
When run without any arguments, log in interactively using a browser. To log in using a device code, pass
--device-code.
To log in as a service principal, pass --client-id and --tenant-id as well as one of --client-secret,
--client-certificate, --client-credential or --client-credential-provider.
azd login [flags]

Options
      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --federated-credential string            The federated token for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
  -o, --output string                          The output format (the supported formats are json, none). (default "none")
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id for the service principal to authenticate with.
      --use-device-code                        When true, log in by using a device code instead of a browser.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd logout
Log out of Azure
Synopsis
Log out of Azure
azd logout [flags]

Options
  -h, --help   Gets help for logout.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd monitor
Monitor a deployed application.
Synopsis
Monitor a deployed application.
Examples:
	azd monitor --overview
	azd monitor -–live
	azd monitor --logs

For more information, go to https://aka.ms/azure-dev/monitor.
azd monitor [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python applications.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd pipeline
Manage GitHub Actions pipelines.
Synopsis
Manage GitHub Actions pipelines.
The Azure Developer CLI template includes a GitHub Actions pipeline configuration file (in the .github/workflows folder) that deploys your application whenever code is pushed to the main branch.
For more information, go to https://aka.ms/azure-dev/pipeline.
Options
  -h, --help   Gets help for pipeline.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline config: Create and configure your deployment pipeline by using GitHub Actions or Azure Pipelines.
Back to top

azd pipeline config
Create and configure your deployment pipeline by using GitHub Actions or Azure Pipelines.
Synopsis
Create and configure your deployment pipeline by using GitHub Actions or Azure Pipelines.
For more information, go to https://aka.ms/azure-dev/pipeline.
azd pipeline config [flags]

Options
      --auth-type string        The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider)
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --provider string         The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines). (default "github")
      --remote-name string      The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline: Manage GitHub Actions pipelines.
Back to top

azd provision
Provision the Azure resources for an application.
Synopsis
Provision the Azure resources for an application.
The command prompts you for the following:

Environment name: The name of your environment.
Azure location: The Azure location where your resources will be deployed.
Azure subscription: The Azure subscription where your resources will be deployed.

Depending on what Azure resources are created, running this command might take a while. To view progress, go to the Azure portal and search for the resource group that contains your environment name.
azd provision [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --no-progress          Suppresses progress information.
  -o, --output string        The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd restore
Restore application dependencies.
Synopsis
Restore application dependencies.
Run this command to download and install all the required libraries so that you can build, run, and debug the application locally.
For the best local run and debug experience, go to https://aka.ms/azure-dev/vscode to learn how to use the Visual Studio Code extension.
azd restore [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.
      --service string       Restores a specific service (when the string is unspecified, all services that are listed in the azure.yaml file are restored).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd template
Manage templates.
Options
  -h, --help   Gets help for template.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template list: List templates.
azd template show: Show the template details.
Back to top

azd template list
List templates.
azd template list [flags]

Options
  -h, --help            Gets help for list.
  -o, --output string   The output format (the supported formats are json, table). (default "table")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Manage templates.
Back to top

azd template show
Show the template details.
azd template show <template> [flags]

Options
  -h, --help            Gets help for show.
  -o, --output string   The output format (the supported formats are json, table). (default "table")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Manage templates.
Back to top

azd up
Initialize application, provision Azure resources, and deploy your project with a single command.
Synopsis
Initialize the project (if the project folder has not been initialized or cloned from a template), provision Azure resources, and deploy your project with a single command.
This command executes the following in one step:
	azd init
	azd provision
	azd deploy

When no template is supplied, you can optionally select an Azure Developer CLI template for cloning. Otherwise, running azd up initializes the current directory so that your project is compatible with Azure Developer CLI.
azd up [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for up.
  -l, --location string       Azure location for the new environment
      --no-progress           Suppresses progress information.
  -o, --output string         The output format (the supported formats are json, none). (default "none")
      --service string        Deploys a specific service (when the string is unspecified, all services that are listed in the azure.yaml file are deployed).
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd version
Print the version number of Azure Developer CLI.
azd version [flags]

Options
  -h, --help            Gets help for version.
  -o, --output string   The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

authors: azure-sdk weikanglim

repo: Azure/azure-dev


text:
[HttpTrigger] Receiving 403 when not sending Expect: 100-continue

We are hosting an Azure Function V4 with runtime type dotnet-isolated.
The package versions are:
Microsoft.Azure.Functions.Worker "1.6.0"
Microsoft.Azure.Functions.Worker.Extensions.Http "3.0.13"
When the Function is deployed to Azure we are facing some issues with larger requests where the request body is over let's say 100 kb. We immediately get a 403 error. This doesn't even log a requests so we don't have any logging we can view. The only way we get it to work is by adding a Expect: 100-continue header. However we don't expect our users to always send this. How can we disable this feature?

@Ultre00 Is this a V3 app or V4? You can check the AzureFunctionsVersion element value in your .csproj file. Do you have a minimal repro you could share? (A github repo will be great)

@kshyju as mentioned this is a V4 function. I also figured out when this happens. It is only in combination with mTLS where the option "clientCertEnabled" is set to true. For now I simply set this to false since we are no longer using mTLS here.

@Ultre00 -- where did you have these configurations set? Is this somewhere in App Service?

@brettsam yes you can set that in the Function App. If you use an ARM template the properties are called
clientCertEnabled in combination with clientCertMode but if you use the UI then you can also do this under configuration > general settings > Client certificate mode

authors: Ultre00 brettsam kshyju

repo: Azure/azure-functions-dotnet-worker


text:
Not able to debug AzF

Hi, I'm not able to debug. Once I attached written PID, I'm getting error on System.PrivateCore.Lib Can't write the message because the call is complete.
When I look inside, I'm gettting this:
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.Azure.Functions.Worker.GrpcWorker.d__14.MoveNext() in D:\a\1\s\src\DotNetWorker.Grpc\GrpcWorker.cs:line 86
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.Azure.Functions.Worker.WorkerHostedService.d__3.MoveNext() in D:\a\1\s\src\DotNetWorker.Core\WorkerHostedService.cs:line 27
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.Extensions.Hosting.Internal.Host.d__9.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at xxx.Program.d__0.MoveNext() in
Do you know, what could be an issue?

@ondrejdurica can you share more details on how you're launching the worker? Is this from VS? Direct command line? If from VS, what does your project configuration look like for the debugging properties?
Thanks!

authors: fabiocav ondrejdurica