text:
[Breadth Coverage] Log Analytics Solution

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.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/zhoxing-ms/azure-cli-extensions.git@dev#subdirectory=src/$EXT&egg=$EXT"

add to S168

authors: azuresdkci yonzhan zhoxing-ms

repo: Azure/azure-cli-extensions


text:
[Container app] Release version 0.3.50

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? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

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.

Container app

source: gharchive/pull-request

authors: Greedygre yonzhan

license: MIT

license_type: permissive

license_source: github-api


text:
az kusto cluster create fails with "Invalid SKU name provided"

Describe the bug
Command Name
az kusto cluster create
Errors:
Invalid SKU name provided

To Reproduce:
az kusto cluster create --location "Central US" --name MyClusterName --resource-group MyRGName --sku D11_v2 --capacity 1
Expected Behavior
Provision Kusto cluster.
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.5.1

Additional Context
I tried all possible values of SKU allowed by the CLI but none of them seem to work. The error happens server-side, here is the relevant part of running with --debug on:
msrest.http_logger : Request headers:
msrest.http_logger :     'Accept': 'application/json'
msrest.http_logger :     'Content-Type': 'application/json; charset=utf-8'
msrest.http_logger :     'accept-language': 'en-US'
msrest.http_logger :     'Content-Length': '72'
msrest.http_logger :     'User-Agent': 'python/3.6.6 (Windows-10-10.0.18362-SP0) msrest/0.6.13 msrest_azure/0.6.3 azure-mgmt-kusto/0.3.0 Azure-SDK-For-Python AZURECLI/2.5.1 (MSI)'
msrest.http_logger : Request body:
msrest.http_logger : {"location": "centralus", "sku": {"name": "D11_v2", "tier": "Standard"}}
msrest.universal_http : Configuring redirects: allow=True, max=30
msrest.universal_http : Configuring request: timeout=100, verify=True, cert=None
msrest.universal_http : Configuring proxies: ''
msrest.universal_http : Evaluate proxies against ENV settings: True
urllib3.connectionpool : Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool : https://management.azure.com:443 "PUT /subscriptions/<redacted>/resourceGroups/<redacted>/providers/Microsoft.Kusto/clusters/<redacted>?api-version=2019-01-21 HTTP/1.1" 400 73
msrest.http_logger : Response status: 400
msrest.http_logger : Response headers:
...
msrest.http_logger : Response content:
msrest.http_logger : {"error":{"code":"InvalidSkuName","message":"Invalid SKU name provided"}}
msrest.exceptions : Invalid SKU name provided

Sounds like the API expects a different specification for the SKU name but CLI restricts this to a small set of values which don't seem to work.

routing to appropriate team

These are old SKUs that were recently removed. We are releasing a new nuget so that you can use the new SKUs. Adding @ilayrn for more information

Thanks! Azure CLI needs to be updated since it restricts the SKU parameter. User can only pick from these SKUs that don't work.

Correct that's why we're working on releasing a new nuget for that to work. AFAIK this was already released, @ilayrn can share the details.

@vladris, we released a new version for Azure CLI with up-to-date support for all the functionality provided by Kusto. To install it, run the command: "az extension add -n kusto". After it's installed, the command should work.

Now I get usage error: --sku [KEY=VALUE ...] for the same command. What is the expected format?

Yes, you should use the same values that appear in the portal, e.g. Dev(No SLA)_Standard_D11_v2. We moved away from enforcing the name on the client-side because SKUs can be added and removed in the backend.

Thanks, I managed to provision a cluster! The updated extension requires separate name-value pairs for SKU name, tier, and capacity. It is a bit tricky to figure out the right combination, is this documented somewhere?
After a bunch of trial and errors,I got it working with name='Dev(No SLA)_Standard_D11_v2' tier='Basic' but a reference for allowed values would really help.

@vladris I'm glad to hear it worked for you. We're going to release the documentation in the coming days and we'll add an example to address your feedback. Thanks!

Hi I cant get it working i have
SubscriptionName='Pay-As-You-Go'
ResourceGroupName='My_RG'
Location='WestUS2'
AzureDataExplorer='myapplicationadx'
SkuName='Dev(No SLA)_Standard_D11_v2'
Capacity=1
az kusto cluster create --name $AzureDataExplorer
--resource-group $ResourceGroupName
--location $Location
--sku SkuName
--capacity $Capacity
not sure what i am missing, please fix the help section of the
az kusto cluster create --help
i am still getting the same error
thanks
Nik

Try this:
az kusto cluster create --cluster-name $AzureDataExplorer
--resource-group $ResourceGroupName
--location $Location
--sku name=SkuName capacity=$Capacity tier=$Tier

+1 on getting this documented, it's not easy to figure it out...

still getting an error
az : ERROR: az kusto cluster create: 'name=Dev(No SLA)_Standard_D11_v2' is not a valid value for '--sku'. See 'az kusto cluster create --help'.

i did run "az extension add -n kusto" got an error
az extension add -n kusto
az : ERROR: No matching extensions for 'kusto'. Use --debug for more information.
At line:1 char:1

az extension add -n kusto

  + CategoryInfo          : NotSpecified: (ERROR: No match...re information.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

I even ran the "az extension add -n kusto --debug" and i git the error
ERROR: cli.azure.cli.core.util : No matching extensions for 'kusto'. Use --debug for more information.
ERROR: No matching extensions for 'kusto'. Use --debug for more information.

@vladris, we released a new version for Azure CLI with up-to-date support for all the functionality provided by Kusto. To install it, run the command: "az extension add -n kusto". After it's installed, the command should work.

i did run it and got the error
z : ERROR: No matching extensions for 'kusto'. Use --debug for more information.
At line:1 char:1

az extension add -n kusto

  + CategoryInfo          : NotSpecified: (ERROR: No match...re information.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

still getting an error
az : ERROR: az kusto cluster create: 'name=Dev(No SLA)_Standard_D11_v2' is not a valid value for '--sku'. See 'az kusto cluster ? create --help'.

Could you please share the full command you ran to create the cluster?

yes i did run ........
az kusto cluster create --name $AzureDataExplorer --resource-group 'IoT_Project_RG' --location westus2 --sku name='Dev(No SLA)_Standard_D11_v2' capacity=1 tier='Basic'
..... and got the error
az : ERROR: az kusto cluster create: 'name=Dev(No SLA)_Standard_D11_v2' is not a valid value for '--sku'. See 'az kusto cluster create --help'.
At line:1 char:1

az kusto cluster create --name $AzureDataExplorer --resource-group 'I ...

  + CategoryInfo          : NotSpecified: (ERROR: az kusto...create --help'.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

Strange, that worked for me. I'll let the product engineers follow up.

can you check this please
....
I even ran the "az extension add -n kusto --debug" and i git the error
ERROR: cli.azure.cli.core.util : No matching extensions for 'kusto'. Use --debug for more information.
ERROR: No matching extensions for 'kusto'. Use --debug for more information.
------ how do you i know that the KUSTO have been installed correctly?????
thanks

I just ran that command and it worked fine for me. Maybe try updating Az CLI?

hi i did reinstall AZURE CLI and Kusto and it did work
I gave you  the code
az kusto cluster create --name $AzureDataExplorer --resource-group ........
and you mentioned it worked , on kkmy side i had to change the code to
az kusto cluster create --**cluster-**name $AzureDataExplorer --resource-group ........
Feedback:
when running anything related to "az kusto ....." the first thing you get is a message in RED that is very very missleading maybe it can be changed, also the information in the --help needs to be updated .
Thank you
Nik

source: gharchive/issue

authors: SQLDataSide ilayrn radennis vladris yungezz

repo: Azure/azure-cli


text:
webapp: Cannot deploy by any means to my WebApp, not using FTP, not using az CLI, not in VS

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp up
Errors:
'NoneType' object has no attribute 'reserved'
Traceback (most recent call last):
python3.8/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 631, in execute
    raise ex
cli/core/commands/__init__.py, ln 695, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 686, in _run_job
    cmd_copy.exception_handler(ex)
...
cli/core/commands/__init__.py, ln 324, in __call__
    return self.handler(*args, **kwargs)
azure/cli/core/__init__.py, ln 574, in default_command_handler
    return op(**command_args)
cli/command_modules/appservice/custom.py, ln 3215, in webapp_up
    current_os = 'Linux' if plan_info.reserved else 'Windows'
AttributeError: 'NoneType' object has no attribute 'reserved'

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 webapp up -g {} -n {} --html

Expected Behavior
Environment Summary
macOS-10.14.6-x86_64-i386-64bit
Python 3.8.2
Installer: HOMEBREW

azure-cli 2.5.1 *

Additional Context

webapp

So, what is happening with this? Did it go straight to trash can? @AzureAppServiceCLI @antcp

@nordquist as per the title the deployment issue is not specific to CLI - are you still seeing this issue.
Few things to consider

When using CLI please upgrade to the newer version from the current issue - seems like you are using a  very old version
App service currently cannot mix windows and linux apps in the same RG, so if you are trying to use the RG that has windows apps you can use it for linux apps & vice versa.

in general az webapp up should take care of #2, if you don't pass a -g in the command but I definitely recommend upgrading to the latest version of azure-cli which has lots of fixes to az webapp up in general.

#14287

It has nothing to do with the version of the CLI as implicated by the fact that there is no way that works. This is the latest message from VS when trying to deploy an Azure Function (..and yes, I have tried setting WEBSITE_RUN_FROM_PACKAGE to 0 (and why this is not default when it never works?)).

The "detailed" error is:
2020-07-10 11:44:55
System.AggregateException: One or more errors occurred. ---> System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. <---

System.Exception: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.

===================

@nordquist given this is CLI I am going to focus on getting this working with CLI -> and if using az webapp up, my recommendation would be to use a more recent version, and run the up command from the context of the DIR where you code to be deployed is. and try creating & deploying a new webapp using webapp up. If this is a function app then this command is not supported for it.
If your question is about run as package deployment then please use this repo to https://github.com/projectkudu/kudu. Hope this helps you.

closing due to lack of response.

authors: nordquist panchagnula yonzhan yungezz


text:
Decouple the code of next in azure-cli-core

In order to decouple the code of az next in azure-cli-core and reduce the impact on the performance and stability of CLI，I set up this issue to track some items that need to be improved:

Register those methods (log_cmd_history,log_latest_error_info,clean_exception_history) in utils as events to move them into next extension
Use environment variables AZURE_CORE_USE_COMMAND_INDEX and reload command table to skip command index.
Call log_latest_error_info in a more appropriate way

Related PR: #15964

Checkbox syntax can be a very good helper 😉:
- [ ] Register those methods (`log_cmd_history`,`log_latest_error_info`,`clean_exception_history`) in utils as events to move them into `next` extension

Core

authors: jiasli yonzhan zhoxing-ms


text:
ProductFunction - ProductDetails function not created , same issue for OrderFunction

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az functionapp create
Errors:

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 functionapp create --resource-group {} --consumption-plan-location {} --name {} --storage-account {} --functions-version {}

Expected Behavior
Environment Summary
Linux-5.4.0-1062-azure-x86_64-with-debian-10.2 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.6.10
Installer: DEB

azure-cli 2.29.0 *

Extensions:
ai-examples 0.2.5
ssh 0.1.6

Additional Context

@alwisr Apologies for the late reply. There is not much information about the error in your issue details section. Were you getting a similar error that is reported in https://github.com/Azure/azure-cli/issues/19903? If Yes, then that issue is now fixed. So please upgrade to the most recent version of Azure CLI and test the behavior. Also since this github thread has been open for quite sometime, so please let us know if you need any further assistance on this. Awaiting your reply.

@alwisr Please let us know if you are still facing this issue. If no further assistance is required on this, can we proceed with closure of this issue? Awaiting your reply.

Thank you. I am sorry. I couldn't respond to you promptly.
On Mon, Feb 14, 2022 at 11:57 PM navba-MSFT @.***>
wrote:

Closed #20035 https://github.com/Azure/azure-cli/issues/20035.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/20035#event-6066526343, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIXQI2VE547IH53NQFGE7TU3DWZTANCNFSM5GWNLJ2A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: alwisr navba-MSFT


text:
az postgres throws an error

Describe the bug
Command Name
az postgres
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'psycopg2._psycopg'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 583, in execute
    parsed_args = self.parser.parse_args(args)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/parser.py", line 261, in parse_args
    return super().parse_args(args)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 1821, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/parser.py", line 284, in parse_known_args
    self._namespace, self._raw_arguments = super().parse_known_args(args=args, namespace=namespace)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 1854, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 2066, in _parse_known_args
    stop_index = consume_positionals(start_index)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 2022, in consume_positionals
    take_action(action, args)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 1931, in take_action
    action(self, namespace, argument_values, option_string)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 1210, in __call__
    subnamespace, arg_strings = parser.parse_known_args(arg_strings, None)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/parser.py", line 284, in parse_known_args
    self._namespace, self._raw_arguments = super().parse_known_args(args=args, namespace=namespace)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 1854, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/argparse.py", line 2091, in _parse_known_args
    self.error(_('the following arguments are required: %s') %
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/parser.py", line 160, in error
    recommender.set_help_examples(self.get_examples(self.prog))
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/parser.py", line 201, in get_examples
    return self.cli_help.get_examples(command,
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/_help.py", line 192, in get_examples
    else self.group_help_cls(self, delimiters, parser)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/help.py", line 253, in __init__
    child.load(options)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/_help.py", line 303, in load
    loader.versioned_load(self, options)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/_help_loaders.py", line 154, in versioned_load
    super(CliHelpFile, help_obj).load(parser)  # pylint:disable=bad-super-call
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/help.py", line 198, in load
    description = getattr(options, 'description', None)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/parser.py", line 241, in __getattribute__
    self.description = self._description() \
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 133, in description_loader
    op = self.get_op_handler(self.op_path)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
    handler = import_module(mod_to_import)
  File "/usr/local/Cellar/python@3.10/3.10.1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/Users/muel42/.azure/cliextensions/db-up/azext_db_up/custom.py", line 15, in <module>
    import psycopg2
  File "/Users/muel42/.azure/cliextensions/db-up/psycopg2/__init__.py", line 51, in <module>
    from psycopg2._psycopg import (                     # noqa
ModuleNotFoundError: No module named 'psycopg2._psycopg'

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 postgres

Expected Behavior
Environment Summary
macOS-12.0.1-x86_64-i386-64bit, Darwin 21.1.0
Python 3.10.1
Installer: HOMEBREW

azure-cli 2.31.0

Extensions:
db-up 0.2.2

Additional Context

Routing to service team.

@kurt-mueller-osumc Can you try the latest version of Azure CLI 2.38.0?


text:
2.54+ breaks at least az monitor activity-log list

Describe the bug
In versions of the az command before 2.54, the command below worked as expected. After 2.54, an exception is thrown. This is very easy to reproduce.
Related command
az monitor activity-log list --resource-id "$CS_ID" --subscription "$SUB_NAME"
Errors
Now, the command fails with the following error trace:
2024-02-22T03:01:16.9303900Z ERROR: The command failed with an unexpected error. Here is the traceback:
2024-02-22T03:01:16.9321542Z ERROR: Expect <class 'str'>, got 0 (<class 'int'>)
2024-02-22T03:01:16.9322288Z Traceback (most recent call last):
2024-02-22T03:01:16.9322702Z   File "/opt/az/lib/python3.11/site-packages/knack/cli.py", line 233, in invoke
2024-02-22T03:01:16.9322988Z     cmd_result = self.invocation.execute(args)
2024-02-22T03:01:16.9323235Z                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9323625Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 664, in execute
2024-02-22T03:01:16.9323890Z     raise ex
2024-02-22T03:01:16.9324654Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 729, in _run_jobs_serially
2024-02-22T03:01:16.9325149Z     results.append(self._run_job(expanded_arg, cmd_copy))
2024-02-22T03:01:16.9325417Z                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9325815Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 698, in _run_job
2024-02-22T03:01:16.9326282Z     result = cmd_copy(params)
2024-02-22T03:01:16.9326515Z              ^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9326898Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 334, in __call__
2024-02-22T03:01:16.9327219Z     return self.handler(*args, **kwargs)
2024-02-22T03:01:16.9327460Z            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9328044Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
2024-02-22T03:01:16.9328550Z     return op(**command_args)
2024-02-22T03:01:16.9328785Z            ^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9329242Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/monitor/custom.py", line 31, in list_activity_log
2024-02-22T03:01:16.9329768Z     return _limit_results(activity_log, max_events)
2024-02-22T03:01:16.9330032Z            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9330474Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/monitor/custom.py", line 95, in _limit_results
2024-02-22T03:01:16.9330810Z     for index, item in enumerate(paged):
2024-02-22T03:01:16.9331231Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_paging.py", line 87, in __next__
2024-02-22T03:01:16.9331708Z     return next(self._page_iterator)
2024-02-22T03:01:16.9332086Z            ^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9332468Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_paging.py", line 43, in __next__
2024-02-22T03:01:16.9332767Z     self._executor(self._next_link)
2024-02-22T03:01:16.9333165Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_command.py", line 250, in executor_wrapper
2024-02-22T03:01:16.9333456Z     executor()
2024-02-22T03:01:16.9337027Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/monitor/aaz/latest/monitor/activity_log/_list.py", line 67, in _execute_operations
2024-02-22T03:01:16.9337850Z     self.ActivityLogsList(ctx=self.ctx)()
2024-02-22T03:01:16.9338592Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/monitor/aaz/latest/monitor/activity_log/_list.py", line 90, in __call__
2024-02-22T03:01:16.9338932Z     return self.on_200(session)
2024-02-22T03:01:16.9339168Z            ^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9339639Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/monitor/aaz/latest/monitor/activity_log/_list.py", line 147, in on_200
2024-02-22T03:01:16.9339954Z     self.ctx.set_var(
2024-02-22T03:01:16.9340519Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_command_ctx.py", line 84, in set_var
2024-02-22T03:01:16.9340807Z     self.vars[name] = data
2024-02-22T03:01:16.9341037Z     ~~~~~~~~~^^^^^^
2024-02-22T03:01:16.9341433Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_value.py", line 76, in __setitem__
2024-02-22T03:01:16.9341750Z     self._data[name] = attr_schema.process_data(data, key=name)
2024-02-22T03:01:16.9342001Z                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9342376Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_type.py", line 234, in process_data
2024-02-22T03:01:16.9342673Z     value[key] = sub_data
2024-02-22T03:01:16.9342894Z     ~~~~~^^^^^
2024-02-22T03:01:16.9343271Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_value.py", line 76, in __setitem__
2024-02-22T03:01:16.9343595Z     self._data[name] = attr_schema.process_data(data, key=name)
2024-02-22T03:01:16.9343845Z                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9344375Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_type.py", line 409, in process_data
2024-02-22T03:01:16.9344678Z     value[idx] = sub_data
2024-02-22T03:01:16.9344888Z     ~~~~~^^^^^
2024-02-22T03:01:16.9345284Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_value.py", line 363, in __setitem__
2024-02-22T03:01:16.9345613Z     self._data[idx] = item_schema.process_data(data, key=idx)
2024-02-22T03:01:16.9345846Z                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9346261Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_type.py", line 234, in process_data
2024-02-22T03:01:16.9346536Z     value[key] = sub_data
2024-02-22T03:01:16.9346757Z     ~~~~~^^^^^
2024-02-22T03:01:16.9347145Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_value.py", line 76, in __setitem__
2024-02-22T03:01:16.9347453Z     self._data[name] = attr_schema.process_data(data, key=name)
2024-02-22T03:01:16.9347710Z                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22T03:01:16.9348476Z   File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_field_type.py", line 48, in process_data
2024-02-22T03:01:16.9349107Z     raise AAZInvalidValueError('Expect {}, got {} ({})'.format(self.DataType, data, type(data)))
2024-02-22T03:01:16.9349551Z azure.cli.core.aaz.exceptions.AAZInvalidValueError: Expect <class 'str'>, got 0 (<class 'int'>)
2024-02-22T03:01:16.9349962Z To check existing issues, please visit: https://github.com/Azure/azure-cli/issues

Issue script & Debug output
az monitor activity-log list --resource-id "$CS_ID" --subscription "$SUB_NAME"
Expected behavior
This command should return valid results, like it did in versions before 2.54
Environment Summary
azure-cli                         2.57.0

core                              2.57.0
telemetry                          1.1.0

Extensions:
azure-devops                      0.26.0

Dependencies:
msal                              1.26.0
azure-mgmt-resource             23.1.0b2

Python location '/opt/az/bin/python3'
Extensions directory '/opt/az/azcliextensions'

Python (Linux) 3.11.7 (main, Jan 31 2024, 05:29:49) [GCC 11.4.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.

Additional context
It seems that our ADO workers were recently upgraded and all pipelines that relied on this command and the ubuntu:latest CI image are broken.

@tkent, as a workaround, could you use 2.54.0 to mitigate the issue during our investigation?

@jsntcy - 2.54.0 is the first breaking version, it's actually 2.53 that is the last working version (you can confirm this using the azure cli docker images)
We've already gone through and manually updated all our pipelines to forcefully downgrade the az-cli to 2.53 as a first step for each job. We'll have to go back and remove the downgrade step across the effected pipelines once this is fixed.

Hi @tkent it's the recent-unexpected integer type value of level in api response, which according to swagger definition should be string type, (and azure cli introduced type validation for responses from version 2.54.0), caused this issue lately. We noticed related service team this issue and will let you know if it gets resolved. Before that, please use azure-cli=2.53.0 to continue your local workflows. Thanks.

Hi @nkiest please have a check about this change of response return field.

@tkent  issue solved by our service team and from my side it works well now. Just let me know if it still cannot work.

authors: AllyW jsntcy tkent


text:
az fails when running in parallel threads

Description
Outline the issue here:
When running az in parallel threads, observing the following error:
ERROR: Error loading command module 'acr'
ERROR: Error loading command module 'acs'
ERROR: Error loading command module 'appservice'
ERROR: Error loading command module 'cdn'
ERROR: Error loading command module 'dla'
ERROR: Error loading command module 'dls'
ERROR: Error loading command module 'iot'
ERROR: Error loading command module 'keyvault'
ERROR: Error loading command module 'lab'
ERROR: Error loading command module 'monitor'
ERROR: Error loading command module 'network'
ERROR: Error loading command module 'rdbms'
ERROR: Error loading command module 'redis'
ERROR: Error loading command module 'resource'
ERROR: Error loading command module 'sf'
ERROR: Error loading command module 'sql'
ERROR: Error loading command module 'storage'
ERROR: Error loading command module 'vm'
ERROR: az: error: argument _command_package: invalid choice: group
usage: az [-h] [--output {json,tsv,table,jsonc}] [--verbose] [--debug]
[--query JMESPATH]
{interactive,ad,feedback,cognitiveservices,cloud,account,batch,component,logout,role,login,cosmosdb,find,configure}
...

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
pip install "azure-cli==2.0.6
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
2.0.6
OS Version: What OS and version are you using?
Answer here:
Ubuntu 16.04
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:
az login

Another randomly observed error:
ERROR: The cloud 'AzureCloud' is not registered.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/azure/cli/main.py", line 36, in main
cmd_result = APPLICATION.execute(args)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/application.py", line 203, in execute
result = expanded_arg.func(params)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/commands/init.py", line 278, in call
return self.handler(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/commands/init.py", line 473, in _execute_command
reraise(*sys.exc_info())
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/commands/init.py", line 450, in _execute_command
result = op(client, **kwargs) if client else op(**kwargs)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/command_modules/resource/custom.py", line 229, in deploy_arm_template
deployment_name, parameters, mode, no_wait=no_wait)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/command_modules/resource/custom.py", line 333, in _deploy_arm_template_core
smc = get_mgmt_service_client(ResourceType.MGMT_RESOURCE_RESOURCES)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/commands/client_factory.py", line 32, in get_mgmt_service_client
api_version=api_version, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/commands/client_factory.py", line 66, in _get_mgmt_service_client
cred, subscription_id, _ = profile.get_login_credentials(subscription_id=subscription_id)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/_profile.py", line 314, in get_login_credentials
account = self.get_subscription(subscription_id)
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/_profile.py", line 291, in get_subscription
subscriptions = self.load_cached_subscriptions()
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/_profile.py", line 276, in load_cached_subscriptions
active_cloud = get_active_cloud()
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/cloud.py", line 283, in get_active_cloud
return get_cloud(get_active_cloud_name())
File "/usr/local/lib/python2.7/dist-packages/azure/cli/core/cloud.py", line 278, in get_cloud
raise CloudNotRegisteredException(cloud_name)
CloudNotRegisteredException: The cloud 'AzureCloud' is not registered.

Closing as this is the same as https://github.com/Azure/azure-cli/issues/3255

authors: derekbekoe dmitsh


text:
[sig image-version update]: re-implement the command

The generic update turns out to be a awkward, so I need to re-implement with more custom logic to make common scenario easier
2 things I came across will update the replicate the regions

SDK can’t handle the serialization correctly with an error thrown out srest.exceptions.SerializationError: Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
The update command gets implemented by directly binding to CRP’s API which expose 2 very similar arguments of “gallery_image_version_name”, “gallery_image_version”, super confusing. So likely, this update command needs to be full customer made, and gets detached from the swagger as much as possible.

The workaround is to run "az sign image-version create" with the new list of the target regions
CC @singhkays


text:
front-door aci command are not available

When will the ACI commands for front-door be available?
Even the CLI Edge build is missing support for them

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

ID: 0e1b5ddd-0054-0175-b689-d20a1349bedb
Version Independent ID: 72ccc1b6-814f-b780-99cd-ab48dfdecb66
Content: az network front-door
Content Source: latest/docs-ref-autogen/ext/front-door/network/front-door.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@jmelvinwork

Thanks, that was the missing piece. Our existing docu should be Extended with this Detail as well
--> https://docs.microsoft.com/de-de/azure/frontdoor/
This issue can be closed

Need to install the extension by running az extension add --name front-door first
https://github.com/Azure/azure-cli-extensions/tree/master/src/front-door

Thanks, this helps. Also note that you need Azure CLI version 2.0.68 or beyond for this extension to be available for installation.

authors: malachma rajarshi-singh tjprescott


text:
[Container] Update container cmdlets to use 2024-05-01-preview version API

Related command
az container
Description

We are in process of releasing some new features, one of them is a new azure resource called ContainerGroupProfile.
For that, added a new command group called az container container-group-profile, this includes commands related to various resource operations like create,list,show,delete and operations related to revisions.
Modified the az container create command to include new container group properties.
Additionally, added the required test scenarios.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

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

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Please fix CI issues

Please fix CI issues

The pr title has been changed.
The checks till points to previous title.
The --deployment-resource-group is not from our pr

for the option_length_too_long, exceptions are already added in linter)eexclusions.yml

AzureCLI-FullTest

@zhoxing-ms - can you please re-trigger the build so the checks can run again on the latest changes so that all checks are successful

@jrathore-msft Please resolve these CI issues

/azp run

replaced by a new PR: https://github.com/Azure/azure-cli/pull/30260

authors: drishtipeshwani09 jrathore-msft kaushik-ms yanzhudd yonzhan zhoxing-ms


text:
doc: better descriptions for 'create-for-rbac --skip-assignment'

Fix #8264

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

@yugangw-msft ping

Done and merge.

This is still unclear to me.
The current doc says
--skip-assignment No-op.
accepted values: false, true
I see several examples that have this parameter but it seems like it may not serve a purpose anymore?
Even in the examples,  I never see it paired with true or false syntax so this is just plain confusing.
Even in the context of this thread the phrase
--skip-assignment
Skip creating the default assignment, which allows the service principal to access resources under the current subscription
It's not clear what the word "which" is referring to.
What "allows the service principal to access resources under the current subscription"?
Adding --skip-assignment
Omitting --skip-assignment
I am thinking the "which statement" is describing the definition of "default assignment" and not the parameter.
In that case by including -skip-assignment the SP would NOT be granted access to the current subscription until a role and/or scope is assigned.  Please help me understand.

authors: agianni tjprescott yugangw-msft


text:
OSA - Remove FQDN parameters and update ensure_osa_aad flow

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

[X] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[X] I adhere to the Command Guidelines.

CC @jim-minter @mjudeikis @amanohar

@tjprescott can you give another look please ? Thanks


text:
Test / Update compute version to azure-mgmt-compute==4.6.0

Test azure/mgmt/compute API Version 2019-03-01

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

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

These tests failed:
test_vm_commands.VMCustomImageTest.test_vm_custom_image_name_conflict
test_vm_commands.VMDiskAttachDetachTest.test_vm_ultra_ssd_disk_update
test_vm_commands.VMDiskAttachDetachTest.test_vm_ultra_ssd_storage_sku
test_vm_commands.VMDiskAttachDetachTest.test_vmss_ultra_ssd_storage_sku
test_vm_commands.VMSSVMsScenarioTest.test_vmss_vms
test_vm_commands.VMManagedDiskScenarioTest.test_vm_managed_disk
test_vm_commands.MSIScenarioTest.test_vmss_explicit_msi
test_vm_commands.VMGalleryImage.test_gallery_e2e


text:
Define transport protobuf model

User story AB#12707964

Reason for Change:
Define protobuf message and services for transport shim
Issue Fixed:
AB#12707965
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Tasks:

[X] Define protobuf file for all Datapath interface methods

Signed-off-by: Nitish Malhotra nitishm@microsoft.com
Notes:

how are you generating the pb.go? would be nice to define gen targets in the makefile for consistency 🙂
even better if you also don't assume protoc is installed and take care of that in a similar fashion as the existing go tools dependency targets.

how are you generating the pb.go? would be nice to define gen targets in the makefile for consistency 🙂 even better if you also don't assume protoc is installed and take care of that in a similar fashion as the existing go tools dependency targets.

Sure I can do that. Are we using it any place else today? I did see a few proto files across the code base.

how are you generating the pb.go? would be nice to define gen targets in the makefile for consistency 🙂 even better if you also don't assume protoc is installed and take care of that in a similar fashion as the existing go tools dependency targets.

Sure I can do that. Are we using it any place else today? I did see a few proto files across the code base.

@nitishm  https://github.com/Azure/azure-container-networking/blob/master/npm/pkg/dataplane/Makefile Check this, Mat has created this MakeFile for auto-generating go mock. You can do something similar. My opinion is this does not have to be in global MakeFile, since we will only generate this once in a while.

To test this out use the following instructions:
Download the protoc binary
./scripts/install-protoc.sh

Install the grpc go gen tool
make tools

Run generate target
cd npm
make generate

@vakalapa can I get another approval. Also any idea why the CI doesn't like it?

authors: nitishm rbtr vakalapa

repo: Azure/azure-container-networking


text:
Update active-directory-manage-groups.md

Added link to PowerShell V2 cmdlets

Hi @RobdeJong, 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 (rodejo). 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;

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

authors: PRmerger RobdeJong azurecla

repo: Azure/azure-content


text:
Update B2C token retrieval endpoint docs

As some people in de comments mention, the Token endpoint URL is incorrect. Also the token endpoint does not return an access_token but an id_token, I'm not sure if this is an error in the docs or in the behaviour of the API but right now it's confusing.

Hi @keesschollaart81, 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;

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

Hey @dstrockis, @swkrish  -  any thoughts on this one? Please drop a sign-off if it looks OK and we will get it merged.

@keesschollaart81 thanks for taking the time to fix these! I fixed the path ordering yesterday, those should be live now.
The scope=client_id thing should actually be supported by the service.  I'm double checking with them on that. I'm going to leave this PR open until I hear back.

I confirmed this should be supported by the service.  Please close out this PR.

#close

authors: BryanLa PRmerger azurecla dstrockis keesschollaart81 ktoliver


text:
Diagnostics: Adds Gateway Request Stats

Pull Request Template
Diagostics Changes
{
   "HttpResponseStatistics":[
      {
         "StartTimeUTC":"2021-03-22T10:11:47.5592589Z",
         "EndTimeUTC":"2021-03-22T10:11:50.3805645Z",
         "RequestUri":"https://127.0.0.1:8081/dbs/7423ce13-7c53-4d86-aa0f-8baafe5350a2/colls/176a5bb7-368b-4444-82
9b-ef5c8308afd8/docs/7dd28a8a-f2d3-4d9d-869a-40754c82db3c",
         "ResourceType":"Document",
         "HttpMethod":"GET",
         "ExceptionType":"System.OperationCanceledException",
         "ExceptionMessage":"The operation was canceled."
      },
      {
         "StartTimeUTC":"2021-03-22T10:11:47.5592589Z",
         "EndTimeUTC":"2021-03-22T10:11:51.2861564Z",
         "RequestUri":"https://127.0.0.1:8081/dbs/7423ce13-7c53-4d86-aa0f-8baafe5350a2/colls/176a5bb7-368b-4444-829b-ef5c8308afd8/docs/7dd28a8a-f2d3-4d9d-869a-40754c82db3c",
         "ResourceType":"Document",
         "HttpMethod":"GET",
         "ExceptionType":"System.OperationCanceledException",
         "ExceptionMessage":"The operation was canceled."
      },
      {
         "StartTimeUTC":"2021-03-22T10:11:47.5592589Z",
         "EndTimeUTC":"2021-03-22T10:11:52.2945455Z",
         "RequestUri":"https://127.0.0.1:8081/dbs/7423ce13-7c53-4d86-aa0f-8baafe5350a2/colls/176a5bb7-368b-4444-829b-ef5c8308afd8/docs/7dd28a8a-f2d3-4d9d-869a-40754c82db3c",
         "ResourceType":"Document",
         "HttpMethod":"GET",
         "StatusCode":"OK"
      }
   ]
}

Do the address resolution statics cover these?

Please verify that there is no perf impact in steady state.

I verified the perf shows no changes in steady state.

authors: asketagarwal j82w kirankumarkolli


text:
Updates az cli resource commands to use go modules

This is an example of what it would like like to deprecate our az cli usage in favor of golang SDK modules.

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/707/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707 --version '' --verbose

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

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707/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/707/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707' -Version '' -Verbose;"

Standalone Binary

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

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

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/707/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707 --version '' --verbose

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

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707/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/707/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707' -Version '' -Verbose;"

Standalone Binary

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

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

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/707/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707 --version '' --verbose

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

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707/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/707/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/707' -Version '' -Verbose;"

Standalone Binary

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

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

authors: azure-sdk wbreza

repo: Azure/azure-dev


text:
[Feature Request] artifacts download should support any version type

Is your feature request related to a problem? Please describe.
I can publish an artifacts with any version string but using the CLI i can only fetch those that conform to semver 2.0.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like the ability to download any artifact that matches a given version string.
az artifacts universal download --organization https://foo.visualstudio.com/ --feed myFeed --version 2020.01.01

Can you give an example of a version that you can publish but not fetch and provide a screenshot of that version in the UI?

This is published by the Azure CNI team for their signed builds. I was trying to fetch it usign the cli which is a little easier to do than the other options.

Sorry for the confusion. Universal here does not refer to a client for downloading any type of package, it refers specifically to downloading a single protocol known as Universal Packages. In order to install a NuGet package, you will need to use a client that supports NuGet. I understand this naming convention is confusing

So when Im looking at an artifact like hte one above and I say connect to the feed it gives me several options. One of those is nuget but there are others like universal packaging, python, npm, etc... Are you saying that none of those would work and the only way to interact with that feed is through nuget?

Each of those refers how to download a different type of package. A feed can contain packages from any of those protocols. In this instance, you are trying to download a NuGet package, so you need a NuGet client.

ah k. That could definitely be made more apparent on those pages. Thanks again.

authors: jchauncey magleaso

repo: Azure/azure-devops-cli-extension


text:
Update Get-MsolUser.md

Change from 'Phone Number' to 'PhoneNumber'
Change from 'Postal Code' to 'PostalCode'
Change from 'Preferred Data Location' to 'PreferredDataLocation'
Change from 'Preferred Language' to 'PreferredLanguage'
Change from 'Proxy Addresses' to 'ProxyAddresses'

Docs Build status updates of commit 2183c6f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-1.0/MSOnline/Get-MsolUser.md
:white_check_mark:Succeeded
View (azureadps-1.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Hello @xavierihee, thanks for your contribution. Please redo your PR with the base branch as master instead live as per the policy.

Closing this. Issue resolved in PR 734.

authors: billmath msewaweru xavierihee

repo: Azure/azure-docs-powershell-azuread


text:
Work on #40

Added eslint grunt task with the minimum configuration.
The complete list of rules can be found in http://eslint.org/docs/rules/

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

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@molant, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, AZPRBOT;

@nomiero done

authors: azurecla molant

repo: Azure/azure-documentdb-node

license: mit

license_source: bigquery


text:
Unable to update Azure Functions to latest (and fixed version) 4.3.0

Description
I am stuck at runtime version 4.28.4.4. I am not sure who's responsibility is this but I am reporting this issue here. Also delete and re creating Azure Functions App doesn't help either.
Steps to reproduce
N/A

The deployment of 4.3.0 has not been completed. You do not need to take any explicit action to get that version (or any newer version of functions runtime), They will be automatically upgraded for you. Keep in mind that, creating a release on GH repo is one of the very first steps of deployment. It takes several days for the deployment & validations to be done.
If you are experiencing an issue with host runtime, please open an issue in the host repo.

authors: kshyju milen-denev

repo: Azure/azure-functions-dotnet-worker


text:
Service Bus 'Message''s label

Since 'Message' is no longer a valid servicebus trigger option, how do you go about retrieving the attributes such as 'Label' from the input message?
This was also asked and not answered in followups to #226

Update: Looks like these properties can be retrieved through FunctionContext;
context.BindingContext.BindingData.TryGetValue("Label", out var label)
This should be documented somewhere

Agreed.
@ggailey777 we can sync up on this and enhancements to the FunctionContext section to cover some core scenarios (sorry, this was missing in preview 5)

@mattchenderson flagging documentation item here, though, this is also addressed with the SDK type bindings work.

We have documentation on the message metadata properties that are populated and available on the FunctionContext. We probably are lacking an example of using that specifically.
The Message type and its Label property are from the now-deprecated Microsoft.Azure.ServiceBus package. I'm not 100% sure what the equivalent is for Azure.Messaging.ServiceBus.ServiceBusReceivedMessage, though I think it may be ApplicationProperties.
You can also bind directly to ServiceBusReceivedMessage from the binding parameter itself, rather than going through the FunctionContext. That is documented here: https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-trigger?tabs=python-v2%2Cisolated-process%2Cextensionv5&pivots=programming-language-csharp#usage

authors: fabiocav mattchenderson onionhammer


text:
Update proto file and grpc packages

We'll be updating the functions host to consume this breaking change (we have a naming conflict between package namespace and name of GRPC service): https://github.com/Azure/azure-functions-language-worker-protobuf/commit/a42a580e5211f89d5cc605a869a48425fccbd880
I'll update this issue with the latest version of the functions host that consumes the proto file changes when it is available!

@elprans _ please udpate grpc packages to the latest version 1.12.0

Please find the artificats here- 2.0.11879. This is a breaking change please address this ASAP as the functions runtime roll out will be starting next week.

@elprans - If you are already made progress on splitting the repos in dev branch, please submit fix for this issue in master branch.

@pragnagopa  I'm having issues with the new host build:
It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.App', version '2.1.0' was not found.
  - Check application dependencies and target a framework version installed at:
      /
  - Alternatively, install the framework version '2.1.0'.

Previous build works fine.  I have dotnetcore-sdk version 2.1.105 installed.

can you please install the latest from https://www.microsoft.com/net/download/windows
We need 2.1.300

I'm on linux, and adter installing 2.1.300 I get:
Unhandled Exception: System.BadImageFormatException: An attempt was made to load a program with an incorrect format.
 (Exception from HRESULT: 0x8007000B)

@fabiocav - Any ideas?

Here's the installation info:
$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.1.300
 Commit:    adab45bf0c

Runtime Environment:
 OS Name:     gentoo
 OS Version:
 OS Platform: Linux
 RID:         gentoo-x64
 Base Path:   /opt/dotnet_core/sdk/2.1.300/

Host (useful for support):
  Version: 2.1.0
  Commit:  caa7b7e2ba

.NET Core SDKs installed:
  2.1.300 [/opt/dotnet_core/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0 [/opt/dotnet_core/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0 [/opt/dotnet_core/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.0 [/opt/dotnet_core/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

@elprans which one of the ZIP files are you using? You want to grab one of the no-runtime bits.

@fabiocav OK, the no-runtime build seems to run, but it doesn't register any functions:
tests/test_cosmosdb_functions.py Hosting environment: Production
Content root path: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions
Now listening on: http://[::]:43743
info: Host.Startup[0]
      Reading host configuration file '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/host.json'
info: Host.Startup[0]
      Host configuration file read:
      {
        "functionTimeout": "00:05:00",
        "http": {
          "routePrefix": "api",
          "maxConcurrentRequests": 5,
          "maxOutstandingRequests": 30
        },
        "queues": {
          "visibilityTimeout": "00:00:10"
        },
        "eventHub": {
          "maxBatchSize": 1000,
          "prefetchCount": 1000,
          "batchCheckpointFrequency": 1
        },
        "logger": {
          "defaultLevel": "Trace",
          "categoryLevels": {
            "Worker": "Trace"
          }
        },
        "healthMonitor": {
          "enabled": true,
          "healthCheckInterval": "00:00:10",
          "healthCheckWindow": "00:02:00",
          "healthCheckThreshold": 6,
          "counterThreshold": 0.8
        }
      }
info: Host.General[0]
      Starting Host (HostId=hammer-1643887886, InstanceId=54fc0803-4aa9-40fd-ad25-069cff6779c8, Version=2.0.11879.0, ProcessId=12552, AppDomainId=1, Debug=False, ConsecutiveErrors=0, StartupCount=1, FunctionsExtensionVersion=)
info: Host.Startup[0]
      Loading custom extension 'EventGridExtensionConfig'
info: Host.Startup[0]
      Loaded custom extension: EventGridExtensionConfig from '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/bin/Microsoft.Azure.WebJobs.Extensions.EventGrid.dll'
info: Host.Startup[0]
      Loading custom extension 'EventHubConfiguration'
info: Host.Startup[0]
      Loaded custom extension: EventHubConfiguration from '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/bin/Microsoft.Azure.WebJobs.EventHubs.dll'
info: Host.Startup[0]
      Loading custom extension 'CosmosDBConfiguration'
info: Host.Startup[0]
      Loaded custom extension: CosmosDBConfiguration from '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/bin/Microsoft.Azure.WebJobs.Extensions.CosmosDB.dll'
info: Host.Startup[0]
      Generating 0 job function(s)
warn: Host.Startup[0]
      No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. config.UseServiceBus(), config.UseTimers(), etc.).

I'm assuming what you have are Python functions, so I'll let @pragnagopa continue to assist as this is a different issue. Now that you have the runtime running, she should be able to help understand why those functions are not being loaded.

Yes. I will look into this.

@elprans - I cannot repro this issue. None of the functions are being indexed? or just the ones that need extensions?

None of the functions get indexed on my end with https://ci.appveyor.com/api/buildjobs/xmbu4p2g9c8a7utu/artifacts/Functions.Binaries.2.0.11879-alpha.no-runtime.zip

@elprans - Please enable verbose logs by adding following in the host.json
"logger": {
    "categoryFilter": {
      "defaultLevel": "Trace"
    },
    "fileLoggingMode": "always"
  }

Here are the logs with trace level enaled:
$ env PYAZURE_WEBHOST_DEBUG=1 pytest -k test_cosmosdb
========================================================================================= test session starts =========================================================================================
platform linux -- Python 3.6.5, pytest-3.6.1, py-1.5.3, pluggy-0.6.0
rootdir: /home/elvis/dev/clients/microsoft/azure-functions-python-worker, inifile: setup.cfg
collected 62 items / 60 deselected

tests/test_cosmosdb_functions.py Hosting environment: Production
Content root path: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions
Now listening on: http://[::]:46797
trce: Host.Startup[0]
      Host configuration applied.
info: Host.Startup[0]
      Reading host configuration file '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/host.json'
info: Host.Startup[0]
      Host configuration file read:
      {
        "functionTimeout": "00:05:00",
        "http": {
          "routePrefix": "api",
          "maxConcurrentRequests": 5,
          "maxOutstandingRequests": 30
        },
        "queues": {
          "visibilityTimeout": "00:00:10"
        },
        "eventHub": {
          "maxBatchSize": 1000,
          "prefetchCount": 1000,
          "batchCheckpointFrequency": 1
        },
        "logger": {
          "fileLoggingMode": "always",
          "categoryFilter": {
            "Worker": "Trace",
            "defaultLevel": "Trace"
          }
        },
        "healthMonitor": {
          "enabled": true,
          "healthCheckInterval": "00:00:10",
          "healthCheckWindow": "00:02:00",
          "healthCheckThreshold": 6,
          "counterThreshold": 0.8
        }
      }
info: Host.General[0]
      Starting Host (HostId=hammer-1643887886, InstanceId=c59b678e-dd57-4f37-979a-80fbd1f261b8, Version=2.0.11879.0, ProcessId=17582, AppDomainId=1, Debug=False, ConsecutiveErrors=0, StartupCount=1, FunctionsExtensionVersion=)
trce: Host.Startup[0]
      Debug file watch initialized.
trce: Host.Startup[0]
      File event source initialized.
trce: Host.Startup[0]
      Workers Directory set to: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/build/webhost/workers
trce: Host.Startup[0]
      Loading worker providers from the workers directory: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/build/webhost/workers
trce: Host.Startup[0]
      Found worker config: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/build/webhost/workers/node/worker.config.json
trce: Host.Startup[0]
      Will load worker provider for language: node
trce: Host.Startup[0]
      Worker path for language worker java: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/build/webhost/workers/java
trce: Host.Startup[0]
      Worker path for language worker node: /home/elvis/dev/clients/microsoft/azure-functions-python-worker/build/webhost/workers/node
trce: Host.Startup[0]
      Function metadata read.
trce: Host.Startup[0]
      Binding providers loaded.
trce: Host.Startup[0]
      Binding providers initialized.
info: Host.Startup[0]
      Loading custom extension 'EventGridExtensionConfig'
info: Host.Startup[0]
      Loaded custom extension: EventGridExtensionConfig from '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/bin/Microsoft.Azure.WebJobs.Extensions.EventGrid.dll'
info: Host.Startup[0]
      Loading custom extension 'EventHubConfiguration'
info: Host.Startup[0]
      Loaded custom extension: EventHubConfiguration from '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/bin/Microsoft.Azure.WebJobs.EventHubs.dll'
info: Host.Startup[0]
      Loading custom extension 'CosmosDBConfiguration'
info: Host.Startup[0]
      Loaded custom extension: CosmosDBConfiguration from '/home/elvis/dev/clients/microsoft/azure-functions-python-worker/tests/cosmosdb_functions/bin/Microsoft.Azure.WebJobs.Extensions.CosmosDB.dll'
trce: Host.Startup[0]
      Extension loading complete.
trce: Host.Startup[0]
      Metadata provider created.
trce: Host.Startup[0]
      Adding Function descriptor providers for all languages.
trce: Host.Startup[0]
      Function descriptors created.
info: Host.Startup[0]
      Generating 0 job function(s)
warn: Host.Startup[0]
      No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. config.UseServiceBus(), config.UseTimers(), etc.).
info: Host.Startup[0]
      Host initialized (338ms)
info: Host.Startup[0]
      Host started (955ms)
info: Host.Startup[0]
      Job host started
info: Host.General[0]
      Host lock lease acquired by instance ID '00000000000000000000000036AAB76E'.

I think the host doesn't find the Python worker.  Has the configuration protocol changed.  Currently, we set the workers:config:path and workers:python:path environment variable.  The first points to the root, and the second points to ${ROOT}/python/worker.py

Yes, I see the Workers Directory set to line is incorrect.

Yes. Correct. Sorry missed mentioning that. You need to set languageWorkers:python:workerDirectory

Here is the build for the current functions host release 2.0.11886

Available in release -  1.0.300-alpha

authors: asavaritayal elprans fabiocav mhoeger pragnagopa

repo: Azure/azure-functions-python-worker


text:
Cannot load a pre trained Keras h5 model inside Python functions

Inferencing from a Keras model seems impossible with this issue:
Keras has an api called load_model which loads a pre-trained model from disk. It does not support loading this from a blob or file storage. It can load this from a mounted disk.
Azure functions on Python must provide a facility to be able to load model files from mounted storage.
Ideally ML libraries must support loading models from cloud like blob storage/file share etc. But they seem to be supporting disk paths.
Observed this with gensim, NLTK and now Keras.
If there is a way to access a specific disk from Python functions - load it from runtime or support SMB, it will bridge this gap to some extent. Here are some GitHub issues raised on the libraries themselves.
https://github.com/nltk/nltk/issues/2127
https://github.com/RaRe-Technologies/gensim/issues/2184
Workaround: Pickle the model while training it. Load the pickled model back. scikit supports this but Keras warns against pickling models, and suggests to go with their API.
The major concern with this workaround is for data scientists to be able to consciously store models in pickle format, which they will reject with passion - and its also wrong for them to persist this way. AWS lambda solves this by allowing disk access.

Works when I did this:
model = load_model(os.path.join(os.getcwd(),"FUNC_APP_NAME","keras-gear.h5"))
But the model is now part of the function app and is uploaded along with function app.
As an alternative, tried the "Bring your own storage" option:
https://blogs.msdn.microsoft.com/appserviceteam/2018/09/24/announcing-bring-your-own-storage-to-app-service/
Did not work after mounting "models" folder from blob storage to /home/site/wwwroot/ folder.
Asking to support "Bring your own storage" pattern with functionapp - this is the key to using functions with ML for inference.

Works when I did this:
model = load_model(os.path.join(os.getcwd(),"FUNC_APP_NAME","keras-gear.h5"))

Good to know that this worked.

Asking to support "Bring your own storage" pattern with functionapp - this is the key to using functions with ML for inference.

I don't think we have the ability to mount an external storage to the container today. Keeping the issue open, to gauge traction. /cc @davidebbo @ahmelsayed

Serverless Python is mostly seen as an inferencing compute target for ML scenarios among the ML python community. This means it should load models that are stored in blob storage. Currently using Docker/Kubernetes, the model is explicitly downloaded from Blob storage into local disk path and ML libraries load models from local disk path.
While ML Libraries need to catch up and load models from Azure blob storage (which might take a while) it is important to stop this gap by getting to load models from local paths. And hence mounting the paths from a custom storage becomes very important.
The "bring your own storage" facility for webapp seems very valuable in this context. While operationalizing models, this can be used readily from a CI/CD pipeline for inference purposes from a function.  I strongly suggest to get this for functionapp if we need functions to do ML inferencing.

@asavaritayal  - the “Bring Your Own Storage” feature in that blog announcement from the team mentions it's for "App Service on Linux and Web App for Containers". Wouldn't it work for Functions in App Service Plans for now? I suspect Consumption plan would be a different story to implement...

      Serverless Python is mostly seen as an inferencing compute target for ML scenarios among the ML python community. This means it should load models that are stored in blob storage. Currently using Docker/Kubernetes, the model is explicitly downloaded from Blob storage into local disk path and ML libraries load models from local disk path.

While ML Libraries need to catch up and load models from Azure blob storage (which might take a while) it is important to stop this gap by getting to load models from local paths. And hence mounting the paths from a custom storage becomes very important.
The "bring your own storage" facility for webapp seems very valuable in this context. While operationalizing models, this can be used readily from a CI/CD pipeline for inference purposes from a function.  I strongly suggest to get this for functionapp if we need functions to do ML inferencing.

I had Keras TF models working in functions in August but only in a container/locally as the 200MB model proved a challenge for the service. I recently got sklearn models working loading them from blob. Originally I wanted to have routes mapped to model versions but as per this issue: https://github.com/Azure/azure-functions-python-worker/issues/230
The inputStream object is missing the BytesIO method .seek.
I worked around the issue for now by loading the models directly from blob from the REST API where I could perform the .seek(0) required for Pickle. joblib implements .seek(0) in the backend while loading.
Here's my getBlob function and associated helper functions:
def getDate():
    date = datetime.utcnow()
    return date.strftime("%a, %d %b %Y %H:%M:%S GMT")

def generateAuth(storageaccount, stringtosign, key):
    encodedstring = bytes(stringtosign, 'utf-8')
    signature = hmac.new(key, msg=encodedstring, digestmod=hashlib.sha256).digest()
    signature = base64.b64encode(signature).decode()
    return "SharedKeyLite "+storageaccount+":"+signature

def getBlob(key, modelVer, storageaccount, modelname):
    url = "https://"+storageaccount+".blob.core.windows.net/"+modelname+"/"+modelVer
    date = getDate()
    stringtosign = "GET\n\n\n\nx-ms-date:"+date+"\nx-ms-version:2018-03-28\n/" \
    +storageaccount+"/"+modelname+"/"+modelVer
    auth = generateAuth(storageaccount, stringtosign, key)
    header = {"Authorization": auth, "x-ms-date": date, "x-ms-version": "2018-03-28"}
    res = requests.get(url, headers=header)
    return BytesIO(res.content)

The object returned by getBlob I'm loading with joblib like this: lemon_model = joblib.load(model)
These aren't large models so the function runs quite quickly even loading models from blob. I am going to test the 200MB Keras TF model with this pattern and see how it performs.

@jmo808 : What is joblib? Are you able to use keras API's themselves to load a model directly from a byte stream? I know Keras API's don't support reading from a blob.

authors: asavaritayal jmo808 nzthiago priyaananthasankar


text:
Building in TeamCity

Hi, not sure if anyone else has run into this, but I am trying to build in TeamCity 2017.1 w/ VS2017 and I am getting this error in Client:
Open in IDE
Table\MobileServiceTable.Generic.cs(367, 61): error CS1061: 'T[]' does not contain a definition for 'AsQueryable' and no extension method 'AsQueryable' accepting a first argument of type 'T[]' could be found (are you missing a using directive or an assembly reference?)
Table\Query\Linq\MobileServiceTableQuery.cs(113, 61): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(148, 46): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(173, 58): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(196, 58): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(219, 58): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(242, 58): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(256, 58): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQuery.cs(270, 58): error CS0103: The name 'Queryable' does not exist in the current context
Table\Query\Linq\MobileServiceTableQueryTranslator.cs(144, 59): error CS0246: The type or namespace name 'Queryable' could not be found (are you missing a using directive or an assembly reference?)
Table\Sync\MobileServiceSyncTable.Generic.cs(145, 73): error CS1061: 'T[]' does not contain a definition for 'AsQueryable' and no extension method 'AsQueryable' accepting a first argument of type 'T[]' could be found (are you missing a using directive or an assembly reference?)

In case anyone else runs into this, the solution is that you cannot do the VS2017 build under the SYSTEM account, build agent has to be running some other (Admin) account. You can prove it to yourself by using psexec to log in as SYSTEM and try running msbuild. No matter what, it will fail with this issue. Start TeamCity agent with another account and it will work.

repo: Azure/azure-mobile-apps-net-client


text:
laz file does not render correctly

I have a laz file that I'm able to display in another 3D tool but it does not render correctly in ARRT.
sessionId: Arrdaf57ddb3e5a84968e2aab1958b6751c

Hi! Thank you for bringing up the issue.
Did the rendering of your model show only a checkerboard background? It's possible that the model you were trying to render is too big for a standard size session. Please double check the sizes here Server sizes - Azure Remote Rendering | Microsoft Learn
If you'd like to share the file for us to investigate, please open a ticket in https://learn.microsoft.com/en-us/azure/remote-rendering/resources/support

I switched to Premium and was able to see the model. Thanks!

Glad to hear! I'm closing this issue, if you have any other problems please let us know :)

repo: Azure/azure-remote-rendering


text:
SQL database Internal Error tracking

A customer reported an issue https://github.com/terraform-providers/terraform-provider-azurerm/issues/7999.
Would you like to track the error with Tracking ID: 'a063eb77-e541-4c95-9edf-a12efc38d938'

Any updates or any other way the public has to track the progress on this?

repo: Azure/azure-rest-api-specs


text:
Updated the resource settings models of following tracked NRP resourc…

…es and related models:
Network Interfaces
Network Security Groups
Virtual Networks
Loadbalancers
Public IP
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

As identified in the automated checks there are breaking changes, Please follow Azure Breaking changes approval request form as defined Breaking Change Process

approved breaking changes since this is a preview api within one year

authors: ArcturusZhang AutorestCI azuresdkci innosam


text:
Second PR for StorSimple 8000 Series ARM APIs.

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Closing this, as this is second PR and still already merged Commits are part of it. Will be raising another PR without earlier commits.


text:
Changed requireServerNameIndication flag type to boolean

Resolved https://github.com/Azure/azure-sdk-for-node/issues/1603 issue

Hi @MikhailTryakhov, 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 (v-mitry). 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;

authors: MikhailTryakhov azurecla


text:
Update default maskingFunction for datamasking rules

Reordering the enum values for maskingFunction in data masking rules.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@yaakoviyun @jaredmoo fyi

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: specification/sql/resource-manager/Microsoft.Sql/2014-04-01/dataMasking.json
Before the PR: Warning(s): 2  Error(s): 1
After the PR: Warning(s): 2  Error(s): 1
Know more about AutoRest Linter Guidelines.
Send feedback and make AutoRest Linter Azure Bot smarter day by day!
Thanks for your co-operation.

@sergey-shandar CI in the middle of being updated, ignore failures today

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: specification/sql/resource-manager/Microsoft.Sql/2014-04-01/dataMasking.json
Before the PR: Warning(s): 2  Error(s): 1
After the PR: Warning(s): 2  Error(s): 1
Know more about AutoRest Linter Guidelines.
Send feedback and make AutoRest Linter Azure Bot smarter day by day!
Thanks for your co-operation.

No modification for AutorestCI/azure-sdk-for-ruby

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-python

authors: AutorestCI azuresdkci nathannfan olydis


text:
[Event Grid] Event grid C# code generation section.

This is the readme.md code generation requirements for azure-sdk-for-net.
Corresponding change can be found at: https://github.com/Azure/azure-sdk-for-net/pull/3600

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@ScottHolden,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

No modification for AutorestCI/azure-sdk-for-ruby

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-python

authors: AutorestCI ScottHolden msftclas


text:
Add missing DeleteBastionShareableLinkByToken API back to swagger

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:

This is a Pull Request for new Microsoft.Network API version (2023-06-01) branch. Endpoint 'DeleteShareableLinksByToken' has been available to public since 2019. It was released together with 'CreateShareableLinks', 'GetShareableLinks' and 'DeleteShareableLinks' endpoints. However, for some reason this 'DeleteShareableLinksByToken' endpoint was not added to the swagger at that time, causing public documentation & SDK missing this endpoint. This PR aims at adding it back to swagger.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Any clarifications you'd like to add? please complete the purpose of PR section

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
Update existing version to fix swagger quality issues in S360.
Other, please clarify:
edit this with your clarification

Any clarifications you'd like to add? please complete the purpose of PR section

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.) Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.) Update existing version to fix swagger quality issues in S360. Other, please clarify: edit this with your clarification

Hello @TimLovellSmith I updated the purpose of this PR

Hello @TimLovellSmith I replied to the comments, could you please review again? Thanks!

I see some lintdiff errors again, so I'm not sure lintdiff is working correctly on this PR @rkmanda
One issue that seems to be mentioned is a cyclic dependency between mfe.json and machineLearningServices.json
 {
2023-09-11T14:58:42.8166189Z           "pluginName": "spectral",
2023-09-11T14:58:42.8166898Z           "extensionName": "@microsoft.azure/openapi-validator",
2023-09-11T14:58:42.8167461Z           "level": "fatal",
2023-09-11T14:58:42.8169476Z           "message": "openapiValidatorPluginFunc: Failed validating:Error: Dependency Cycle Found: file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/machineLearningServices.json -> file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json -> file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/machineLearningServices.json"
2023-09-11T14:58:42.8170932Z         },

...or at least make sure the dependencies are unidirectional

Tagging this as FixS360 since purpose is to revise docs for existing workign API.

Tagging so the change to an existing stable version can be signed off for breaking changes. Even though it looks mostly safe to me.

My mistake, breaking change review not required because its updating a release branch.

authors: TimLovellSmith msftsijielin


text:
Correcting the NodeConfiguration Model and Example

Fixing the NodeConfiguration Model for the PUT call.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-libraries-for-java

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

authors: AutorestCI vrdmr