text:
az login fails

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
The command failed with an unexpected error. Here is the traceback:
HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /organizations/v2.0/.well-known/openid-configuration (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x066A6A48>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connection.py", line 174, in _new_conn
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/util/connection.py", line 73, in create_connection
  File "socket.py", line 955, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 699, in urlopen
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 382, in _make_request
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 1010, in _validate_conn
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connection.py", line 358, in connect
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connection.py", line 186, in _new_conn
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x066A6A48>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/adapters.py", line 439, in send
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 783, in urlopen
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 755, in urlopen
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/util/retry.py", line 574, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /organizations/v2.0/.well-known/openid-configuration (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x066A6A48>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/profile/custom.py", line 139, in login
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/_profile.py", line 154, in login
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/auth/identity.py", line 153, in login_with_auth_code
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/auth/identity.py", line 112, in _msal_app
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 1685, in __init__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 533, in __init__  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/authority.py", line 120, in __init__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/authority.py", line 175, in tenant_discovery
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/individual_cache.py", line 269, in wrapper
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/sessions.py", line 555, in get
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/sessions.py", line 542, in request  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/sessions.py", line 655, in send
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/adapters.py", line 516, in send
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /organizations/v2.0/.well-known/openid-configuration (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x066A6A48>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

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 login --tenant {}

Expected Behavior
Environment Summary
Windows-10-10.0.19044-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.47.0

Extensions:
aks-preview 0.5.79

Dependencies:
msal 1.20.0
azure-mgmt-resource 22.0.0

Additional Context

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

I had a DNS ISP provider error

Duplicate of #20367

authors: bebound rgnima yonzhan


text:
[AppService] Hybrid connections improve error/help msg

Description
Customer requested improved error message when hybrid connection does not exist - as the command will only add an existing hybrid connection and not create a new. Currently the error message is "Parameter 'resource_group_name' must have length greater than 1".
The PR also adds support for Linux, which has been possible for a while.
Testing Guide
az webapp hybrid-connection add -g -n --namespace --hybrid-connection
History Notes

[AppService] az webapp hybrid-connection add: Improve help/error message and unblock Linux

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.

AppService

source: gharchive/pull-request

authors: madsd yonzhan

repo: Azure/azure-cli

license: MIT

license_type: permissive

license_source: github-api


text:
{CI} Test split automation full test and automatic test scheduling

Description

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.

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

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

CI


text:
Add LogStreaming for Jobs

Related command
az containerapp job logs show
Description
Add log streaming functionality to jobs
Testing Guide
TBD
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.

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

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

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

Please add some test cases for these new feature

Please resolve these CI issues

This feature is implemented in https://github.com/Azure/azure-cli-extensions/pull/7454

authors: lihaMSFT yonzhan zhoxing-ms


text:
ERROR: failed to allocate gateway (x.x.x.x): No address returned

my docker host has 2 interfaces and i'm using the CNM driver:

eth0 with 10.4.70.11/24
eth1 with 10.4.71.201 (and in the azure vnet also 10.4.71.11, 12, 13, 14,... assigned)

when starting a docker container, a bridge name azure3 on eth1 and a interface for the container is being created. the container get's an ip from the available ips and i can reach the container from the host and from hosts that are in the 10.4.70.0/24. so far so good.
however - i can't reach the container from another subnet (and the loadbalancer can't as well). the problem is that the default gateway of the host is 10.4.70.1 which is bound to eth0. so the incoming packets will arrive via the 10.4.71.0/24 subnet on eth1 but it will try to send back the packets on eth0.
so i tried to pass the default gateway for the docker container (docker-compose.yml):
   ...
    networks:
      crate:
        ipv4_address: 10.4.71.11

networks:
  crate:
    driver: azure-vnet
    ipam:
      driver: azure-vnet
      config:
        - subnet: 10.4.71.0/24
          gateway: 10.4.71.1

this yields in an error: ERROR: failed to allocate gateway (10.4.71.1): No address returned.
the logfile shows:
Nov 08 18:25:27 docker-1 azure-vnet-plugin[12111]: 2017/11/08 18:25:27 [ipam] Requesting address with address:10.4.71.1 options:map[azure.address.type:gateway azure.address.id:].
Nov 08 18:25:27 docker-1 azure-vnet-plugin[12111]: 2017/11/08 18:25:27 [ipam] Address request completed with address:<nil> err:Address not found.
Nov 08 18:25:27 docker-1 azure-vnet-plugin[12111]: 2017/11/08 18:25:27 [azure-vnet-ipam] Sent *cnm.errorResponse &{Err:Address not found}.

the second approach i tried was modifying the routing table of the host so that traffic originating from the 10.4.71.0 ips is being sent over eth1. i created a second route table that sends the traffic from that ip back to that gateway
ip route add 10.4.71.0/24 dev azure3 src 10.4.71.201 table 2
ip route add default via 10.4.71.1 dev azure3 table 2
ip rule add from 10.4.71.201/32 table 2
ip rule add to 10.4.71.201/32 table 2

after that the main ip (10.4.71.201) is reachable from other subnets. but the ip's inside the docker containers are still not reachable.
another problem is that azure-vnet-plugin also wipes this routing table and i need to create it again.
what's the best/correct/working approach to get CNM working with two interfaces? how to properly set up routing?

@jodok We can take a look, but the return packets not being sent on the same NIC is possibly due to the default weak host routing in the Linux. I am not sure if this issue is specific to the container scenario. Have you looked into setting up strong host routing?

ehat do you mean with "strong routing"? creating a route table in the azure portal an route an entire subnet to the host interface?

Closing stale issue. Can revisit later if anything changes.

source: gharchive/issue

authors: jodok saiyan86 sharmasushant

repo: Azure/azure-container-networking


text:
fix: [NPM] add check for invalid /0 cidr

Reason for Change:

This fixes an issue where we were not throwing an error for CIDRs whose IPs were not 0.0.0.0 and ended with /0 during translation. Any CIDR with [ip]/0 is invalid unless IP is 0.0.0.0.
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[x] adds unit tests

Notes:
Add check for invalid /0 CIDRs

/azp run


text:
Typos fixed in single article

Added missing $ for those who copy & paste these to command line and updated the version number.

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

Thanks for the updates!

authors: azurecla jukra tysonn

repo: Azure/azure-content


text:
Update hdinsight-apache-spark-resource-manager.md

Spelling problem on "allocated"

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

the border is visible. please publish.

sorry, wrong item:)

authors: Jim-Parker azurecla markgar


text:
(Hold until ADL .NET SDK ship) Updating SDK sample code and instructions

(Hold until ADL .NET SDK ship) Updating SDK sample code and instructions

Modified SDK sample code and installation instructions
Added App authentication example (in addition to updated User auth example)

Hi @matt1883, 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 (mahi). 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;

Hi @matt1883, 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 (mahi). 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;

#sign-off

authors: azurecla matt1883 nitinme


text:
proposing change

seems reasonable

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

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

@NarayanAnnamalai - Please review this change. Also, if the change is okay, change the note formatting to markdown please. Thanks.

@NarayanAnnamalai
In addition to the requested change to the note there is also a typo that needs to be corrected in this PR.
Trafic to Traffic

fixed, thanks

Hi @4c74356b41, thanks for your contribution to improving Azure documentation. Due to an issue with merge conflict, I am requesting you to please close this PR, the changes have been made to the repository already. Thanks again.

#please-close

authors: 4c74356b41 Ja-Dunn NarayanAnnamalai PRmerger azurecla carmonmills


text:
Change feed processor with lease container partition key other than /id

Is your feature request related to a problem? Please describe.
The change feed processor requires lease container with specific partition name. This requires me to provision a dedicated container using at least 100 RU even in my dev/test environments.
Describe the solution you'd like
Allow to use arbitrary partitioned lease container.

The lease container is to be used exclusively by the Change Feed Processor, not shared with other load or operations. It can be shared with multiple Change Feed Processor instances, but its main goal is to be the state store for the Processor.
The Change Feed Processor needs to know the Partition Key to execute its operations and hence the requirement to be partitioned by /id. If you provided a container with a different Partition Key, then it could interfere with the operations and schema the Change Feed Processor uses (for example, creating hot partitions if the PK is an attribute not used by CFP or generating failures in the queries or operations if the PK matches one of the attributes used by the lease schema).
Reusing the same container to do operations can generate data corruption (deleting or altering leases while the Change Feed Processor instances are running) so it is not recommended.
There are no plans currently to provide support for custom partitioned containers.

Closing as the question has been answered, no current plans to support a custom partitioning schema.
Pull model without the lease container requirement is in the works, see https://github.com/Azure/azure-cosmos-dotnet-v3/issues/831

authors: ealsur skwasiborski


text:
Strongly typed Patch operations via Expressions

Now that Patch support is in GA, it'd be nice to add the Linq/expression-based strongly-typed support that the library has for most other operations. Among other things, this would be type-safe, independent of the specific JsonSerializer used, and more easily composable.
Currently, only the ItemResponse<T> from PatchItemAsync<T> uses its generic type.
If I understand correctly, there are two parts of the API that are currently "weakly typed".

The path to update.

Current: string. e.g. PatchOperation.Add("/nonExistentParent/Child", "bar").
Proposed: an Expression. e.g. PatchOperation.Add(x => x.NonExistentParent.Child, "bar").
The implementation of this is pretty simple; you can build a JsonPointer out of the expression, using the contract resolver from the JsonSerializer to determine the names for each property (e.g. see my StackOverflow answer.)

Filter predicates.

Current: string. e.g. "from c where (c.TotalDue = 0 OR NOT IS_DEFINED(c.TotalDue))"
Proposed: A Predicate expression. e.g. c => c.TotalDue = 0 || c.TotalDue == null
This seems like it could be implemented with the internals of the SDK's Linq engine, which I am unfamiliar with.

Sounds like a good idea

That's a great suggestions @Arithmomaniac. We will track it part of backlog.

The path to update.

Current: string. e.g. PatchOperation.Add("/nonExistentParent/Child", "bar").
Proposed: an Expression. e.g. PatchOperation.Add(x => x.NonExistentParent.Child, "bar").
The implementation of this is pretty simple; you can build a JsonPointer out of the expression, using the contract resolver from the JsonSerializer to determine the names for each property (e.g. see my StackOverflow answer.)

Note: Going this route would mean that we would also have to account for array indexes when creating these pointers like/nonExistentParent/Child/0 and adding to arrays like /nonExistentParent/Child/-. Still trivial. Just something to we must not overlook. There is no reason to solution it here. I already have an idea of the implementation details. Thanks.

Update: Current plan is to cover it as sample to start with and then later explore first class API support.

authors: Arithmomaniac imakhlin kirankumarkolli philipthomas-microsoft


text:
Application Insights only tracking some types of calls

Describe the bug
We have a .net 6 application that reads/writes to cosmos collections via CosmosClient, and also has a ChangeFeedProcesser monitoring changes.
However, it seems that only the ChangeFeed related operations show up under dependencies in the Application Insights traces for the application.
When looking at the SDK source, it looks like telemetry is tracked via Open Telemetry. Should we not expect this to work with the standard Application Insights SDK?
Expected behavior
I would expect to see all the queries/updates through CosmosClient show as dependencies in Application Insights
Environment summary
We are using these nuget packages:

Microsoft.ApplicationInsights.AspNetCore(2.21.0)
Microsoft.Azure.Cosmos(3.34.0)

Running on Web Apps 4 containers in Azure (but the same thing is true for local dev box)

@mortenbock you need to upgrade the Appinsights SDK version to this https://www.nuget.org/packages/Microsoft.ApplicationInsights/2.22.0-beta3

@sourabh1007 Thank you.
In this related PR https://github.com/microsoft/ApplicationInsights-dotnet/pull/2635 it is mentioned:

You can enable distributed tracing for Cosmos with the following API: TODO, add a link to cosmos docs.

And I see you are mentioned in terms of providing a link to how this works with cosmos.
Is there any documentation for this?
We would like to trace some document changes, that we process via the ChangeFeed, similar to how it would be traced with a service bus queue for example.
I found this example on how to do this generally https://medium.com/nerd-for-tech/correlate-background-jobs-or-integration-events-with-the-initial-command-in-application-insights-2b549e574a51 but I am wondering if there i a built in feature for this?

Sorry I missed that. Yes, it is under preview, you need to have "Preview" package to use this feature.
You can refer this for example.
https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/sdk-observability?tabs=dotnet#configure-the-application-insights-sdk
Please let us know if you see any issue with this.

I'm getting something, but not quite informational.
Using:

Microsoft.ApplicationInsights.AspNetCore 2.22.0-beta3
Microsoft.Azure.Cosmos 3.34.0-preview

So these dependency calls are going through the TCP mode, and are getting tracked as n/a, so there's not a lot of info about what they are tracing.

you can ignore n/a activities. It will be removed in future AppInsight SDK releases.
AppInsight sdk will allow only operation level activities i.e ServiceBusProcessor.ProcessMessage if you click on that you should see some information related to that operation in the properties section. along with that you should see "request diagnostics" generated if latency is exceeding threshold i.e https://github.com/Azure/azure-cosmos-dotnet-v3/blob/8684535d233ea6a7147d857fae9a6c69e467c827/Microsoft.Azure.Cosmos/src/Telemetry/OpenTelemetry/DistributedTracingOptions.cs#L17

Right now, We are covering only Operation level call and its corresponding information in custom properties. Here is the example of a changefeed operation.

If you click on "Trace and Events" section, you will see a long JSON string with request information (if latency was higher than the threshold)

Closing due to inactivity. @mortenbock please feel free to reopen it, if you have further questions or feedback.

@Punit002 You can use this sample for reference https://github.com/Azure/azure-cosmos-dotnet-v3/tree/master/Microsoft.Azure.Cosmos.Samples/Usage/ApplicationInsights

Please open a new issue, if you have any question.


text:
Query: Adds support for multi-value Group By query for LINQ

Pull Request Template
Description
This PR adds the ability to translate LINQ query to SQL query with multiple items in the SQL select clause. This is achieved through the value clause using NewExpression
Type of change
Please delete options that are not relevant.

[] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] This change requires a documentation update

Closing issues
To automatically close an issue: closes #IssueNumber

Semi-related issues in case they are easy to address in the same block of work:

https://github.com/Azure/azure-cosmos-dotnet-v3/issues/2607
https://github.com/Azure/azure-cosmos-dotnet-v3/issues/3728
(I'd love records support as it would let me remove some horrendous expression tree manipulation workarounds)


text:
What is offerEnableRUPerMinuteThroughput when creating collections?

When creating a collection, then offerEnableRUPerMinuteThroughput can be supplied in the options. I couldn't find any documentation on what this really means. In the Azure Portal one must select a "Throughput", there is no option to enable or disable anything.

It was a way of provisioning requests units when you run out your RUs (pp. 258-263) but it was retired.

Closing this issue due to age. Active development of our Python SDK has moved to https://github.com/Azure/azure-sdk-for-python. We have also released 4.0 which includes many updates and new features. If this issue still needs our attention, please reopen it in the new repository.

authors: letmaik nuno-andre southpolesteve

repo: Azure/azure-cosmos-python


text:
[Issue] nil pointer dereference if service has no endpoints

Output from azd version
azd version 1.9.4 (commit 60d7a770c73289e303a539babf5965e638843227)
Describe the bug
nil pointer dereference if a service has no endpoints.
2024-07-03T07:17:03.6009494Z Deploying service migrationservice
2024-07-03T07:17:04.9970512Z Deploying service migrationservice (Logging in to registry)
2024-07-03T07:17:06.4286829Z Deploying service migrationservice (Pushing container image)
2024-07-03T07:17:17.0085129Z Deploying service migrationservice (Updating container app)
2024-07-03T07:17:17.0151392Z panic: runtime error: invalid memory address or nil pointer dereference
2024-07-03T07:17:17.0177186Z [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x55e6aed60f8a]
2024-07-03T07:17:17.0177607Z
2024-07-03T07:17:17.0180145Z goroutine 482 [running]:
2024-07-03T07:17:17.0181536Z github.com/azure/azure-dev/cli/azd/pkg/apphost.ContainerAppManifestTemplateForProject(0xc00049b2e0?, {0xc00049b2e0, 0x10}, {0x1?})
2024-07-03T07:17:17.0187508Z 	/mnt/vss/_work/1/s/cli/azd/pkg/apphost/generate.go:209 +0xa4a
2024-07-03T07:17:17.0188259Z github.com/azure/azure-dev/cli/azd/pkg/project.(*dotnetContainerAppTarget).Deploy.func1(0xc001224990)
2024-07-03T07:17:17.0188944Z 	/mnt/vss/_work/1/s/cli/azd/pkg/project/service_target_dotnet_containerapp.go:203 +0xa6d
2024-07-03T07:17:17.0189359Z github.com/azure/azure-dev/cli/azd/pkg/async.(*TaskWithProgress[...]).Run.func1()
2024-07-03T07:17:17.0189665Z 	/mnt/vss/_work/1/s/cli/azd/pkg/async/task.go:144 +0xfd
2024-07-03T07:17:17.0190075Z created by github.com/azure/azure-dev/cli/azd/pkg/async.(*TaskWithProgress[...]).Run in goroutine 458
2024-07-03T07:17:17.0190376Z 	/mnt/vss/_work/1/s/cli/azd/pkg/async/task.go:140 +0x1c5
2024-07-03T07:17:17.1984872Z NativeCommandExitException: /home/vsts/work/_temp/cf44a0ec-3e77-4d46-87f4-9ded6f55697b.ps1:7
2024-07-03T07:17:17.1985858Z Line |
2024-07-03T07:17:17.1986669Z    7 |  azd up --no-prompt
2024-07-03T07:17:17.1987154Z      |  ~~~~~~~~~~~~~~~~~~
2024-07-03T07:17:17.1987611Z      | Program "azd" ended with non-zero exit code: 2.
2024-07-03T07:17:17.3215739Z ##[error]PowerShell exited with code '1'.

To Reproduce

Use .NET Aspire.
Create a worker project (<Project Sdk="Microsoft.NET.Sdk.Worker">) and add it to the app model
Provision the infrastructure & try to deploy the service with azd deploy (doesn't matter if it's azd up or azd provision & azd deploy) -> above exception is thrown
If you add an arbitrary endpoint using WithHttpEndpoint(), the issue doesn't occur.

Expected behavior
The service is deployed without issue.
Additional context
The problem doesn't occur with azd version 1.9.3 (commit e1624330dcc7dde440ecc1eda06aac40e68aa0a3)

@vhvb1989 can you take a look?

@dab-abittner thank you for reporting this issue.
We have merged a fix for this which you should be able to use from daily-build in a couple hours.

repo: Azure/azure-dev


text:
Remove service calls for location and subscription defaults in UI prompt

Currently, the concept of a default.location and default.subscription is tied to the UI selection. For the UI selection, it's not important to validate the default configuration's validity, and it is preferred that the UI simply chooses no default, or a hardcoded default, if the default configuration isn't valid.
This change removes the extra validation we're performing to validate account defaults. The API and implementation for validated defaults is still available in case we want better guarantees for other use-cases.

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

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

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

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

Standalone Binary

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

MSI

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

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

Documentation

learn.microsoft.com documentation

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

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

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

See also

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

azd config
Manage the Azure Developer CLI user configuration.
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
Available since azure-dev-cli_0.4.0-beta.1.
The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.
The default value of the config directory is:

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

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

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

See also

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

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

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

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

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

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

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

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

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

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

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

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

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

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

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

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

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

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

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

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

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

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

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

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

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

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

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

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

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

Examples
azd config unset defaults.location

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

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

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

azd env: Manage environments.
Back to top

azd env list
List environments.
azd env list [flags]

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

See also

azd infra create: Provision the Azure resources for an app.
azd infra delete: Delete Azure resources for an app.
Back to top

azd infra create
Provision the Azure resources for an app.
Synopsis
Provision the Azure resources for an app.
The command prompts you for the following values:

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

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

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

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

See also

azd infra: Manage Azure resources.
Back to top

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

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

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

See also

azd infra: Manage Azure resources.
Back to top

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

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

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

See also

Back to top

azd pipeline
Manage GitHub Actions or Azure Pipelines.
Synopsis
Manage GitHub Actions or Azure Pipelines.
The Azure Developer CLI template includes a GitHub Actions and an Azure Pipeline configuration file in the .github/workflows and .azdo/pipelines directories respectively. The configuration file deploys your app whenever code is pushed to the main branch.
For more information, go to https://aka.ms/azure-dev/pipeline.
Options
  -h, --help   Gets help for pipeline.

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

See also

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

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

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

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

See also

azd pipeline: Manage GitHub Actions or Azure Pipelines.
Back to top

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

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

azd template: Manage templates.
Back to top

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

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

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

See also

azd template: Manage templates.
Back to top

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

/check-enforcer override

authors: azure-sdk weikanglim


text:
add run bash artifact file

Copying from devtestlabtest. Tested with a Linux VM in dev environment, and verified that custom script ran (because it put info in a file).

Looks good to me!

authors: drwill-ms shichaoh

repo: Azure/azure-devtestlab

license: mit

license_source: bigquery


text:
fixing issue where AzureActiveDirectoryCredentials.AccessToken is null

Fixes Issue #59.

Would this let me fix the AAD case here and get a client directed flow in e2e https://github.com/Azure/azure-mobile-apps-net-server/blob/master/e2etest/Controllers/Table/AuthenticatedController.cs#L52?

I believe so, yes.

Looks good

authors: aziel brettsam phvannor

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


text:
After clearing Storage container LegalHold, delete storage account returns 409 Error

create storage account
create container
set legal holds
update legal holds
clear legal holds
destroy all
6.1 get container:
GET /subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429/blobServices/default/containers/vhds?api-version=2019-06-01 HTTP/1.1

Response:
{"id":"/subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429/blobServices/default/containers/vhds","name":"vhds","type":"Microsoft.Storage/storageAccounts/blobServices/containers","etag":""0x8D8771E1940016B"","properties":{"deleted":false,"remainingRetentionDays":0,"defaultEncryptionScope":"$account-encryption-key","denyEncryptionScopeOverride":false,"publicAccess":"None","leaseStatus":"Unlocked","leaseState":"Available","lastModifiedTime":"2020-10-23T06:37:22.0000000Z","legalHold":{"hasLegalHold":false,"tags":[]},"hasImmutabilityPolicy":false,"hasLegalHold":false}}
Date: Fri, 23 Oct 2020 06:37:55 GMT
Etag: "0x8D8771E1940016B"
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 9c17c7ce-af00-032b-8ba0-307aa9a5f31d
X-Ms-Ratelimit-Remaining-Subscription-Reads: 11976
X-Ms-Request-Id: c0ed5a57-21ae-48da-92ef-228f20ed0e58
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201023T063755Z:bf0f604d-9cb1-44e3-baf2-5418c8627fc5
6.2 container deleted successfully
DELETE /subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429/blobServices/default/containers/vhds?api-version=2019-06-01 HTTP/1.1
Response:
HTTP/2.0 200 OK
Date: Fri, 23 Oct 2020 06:38:00 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 9c17c7ce-af00-032b-8ba0-307aa9a5f31d
X-Ms-Ratelimit-Remaining-Subscription-Deletes: 14999
X-Ms-Request-Id: df503eb9-7d57-49bd-9e26-df9a61c3f125
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201023T063800Z:dc201919-ed23-4dc2-8ac3-db79f5490f91
Content-Length: 0
6.3 account delete return 409 Error
DELETE /subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429?api-version=2019-06-01 HTTP/1.1
Response:
Date: Fri, 23 Oct 2020 06:38:01 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 9c17c7ce-af00-032b-8ba0-307aa9a5f31d
X-Ms-Ratelimit-Remaining-Subscription-Deletes: 14999
X-Ms-Request-Id: 2d91e345-718a-48ba-8962-bedd998021b8
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201023T063802Z:a49c09e8-a612-417b-baf2-b98eddd774ee
{"error":{"code":"AccountProtectedFromDeletion","message":"Account acctestacc88429 Containers vhds have legal hold."}}

@zfchen95, @Himanshu Chhabra
It seems a server issue, would you please help to look?

Fixed: https://msazure.visualstudio.com/One/_git/Storage-SRP/pullrequest/3714293

Thanks @HimanshuChhabra

authors: HimanshuChhabra blueww yupwei68

repo: Azure/azure-rest-api-specs


text:
Data Masking settings for Diagnostic

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] 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

@allenjzhang Could you merge?

authors: AutorestCI promoisha


text:
Add new APIs under Microsoft.App

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[x] SDK of Go
[ ] PowerShell
[x] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] 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

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[X] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi, @xwang971. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.


text:
[DO NOT MERGE] Changes to validate a mitigation we put in place for OpenAPI preview

DO NOT MERGE

Issue being tested was mitigated. Closing.


text:
[Hub Generated] Review request for Microsoft.ContainerService/aks to add version stable/2023-07-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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] public repo review queue, private repo review queue
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
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.
[ ] Other, please clarify:

edit this with your clarification

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:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] 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.

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.

Hey @JeffreyRichter, could you please help approve the breaking change? The CI Breaking Change(Cross-Version) found 3 unique violations.

The changed constraints are introduced in commit #fb4849d.

These restrictions have existed on the server side for a long time, and the change is to write them down explicitly in api specs, which might help avoid users from specifying invalid values.
The change has been approved and applied to previous preview API version 2023-06-02-preview, see comment.

feature owner @UtheMan

Hey @msyyc, could you please help approve the Python SDK breaking change?

In short, I could help confirm this is expected based on the draft PR #4271.
In detail, the released SDK 25.0.0 does not include latest preview API 2023-06-02-preview and there are some difference on this model definition between stable and preview APIs. And this PR is adding a new stable API 2023-07-01, the definition of ManagedClusterWorkloadAutoScalerProfileVerticalPodAutoscaler is identical with previous stable API 2023-06-01.

Hey @msyyc, could you please help approve the Python SDK breaking change?
In short, I could help confirm this is expected based on the draft PR #4271.
In detail, the released SDK 25.0.0 does not include latest preview API 2023-06-02-preview and there are some difference on this model definition between stable and preview APIs. And this PR is adding a new stable API 2023-07-01, the definition of ManagedClusterWorkloadAutoScalerProfileVerticalPodAutoscaler is identical with previous stable API 2023-06-01.

Approved

authors: FumingZhang msyyc


text:
Adding April Swagger For GA

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.

Automation for azure-libraries-for-java

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

@ravbhatnagar Could you check if it was approved before?

@samkreter according to swagger spec specifications https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-13 readOnly attribute can be applied only to properties i.e. you should mark each field under properties as readOnly and not the type itself. Could you revise your pr?

@hovsepm Just finished the changes you requested, but there is a python CI test failing that looks like it is trying to use the Preview version.  Any ideas?

@samkreter once ARM team will sing off on the new stable version we will be able to merge.

Signing off from ARM side.

authors: AutorestCI hovsepm ravbhatnagar samkreter sergey-shandar


text:
update typescript.md for notificationhubs

to update js sdk client name avoid unnecessary breaking changes.

_ No description provided. _

Pease do delete the description.

_ No description provided. _

Pease do delete the description.

updated.

authors: kazrael2119 qiaozha raosuhas


text:
Add azure-sdk-for-js to networking readme.md

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.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

authors: AutorestCI kpajdzik


text:
chore: jsonfmt commerce

Ran jsonfmt -w "specification/commerce/**/*.json"

Can one of the admins verify this patch?

Automation for azure-sdk-for-python
Nothing to generate for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java
A PR has been created for you:
https://github.com/Azure/azure-sdk-for-java/pull/3659

Automation for azure-sdk-for-go
Nothing to generate for azure-sdk-for-go

authors: AutorestCI azuresdkci nschonni


text:
DoNotMerge | Add a new kusto version with changes

The main changes in this PR:
Add a new version
Add a path for 'database move command'
Add a new property enablePurge for ClusterProperties

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask tih@microsoft.com (or NullMDR in github) for additional help.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: zoharHenMicrosoft sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Can one of the admins verify this patch?

Hi @zoharHenMicrosoft there are too many services get changed in this pr, and I believe some of them are just format change. I suggest you revert those changes on those services that you do not want to update. We can find another way to fix the formatter CI.

Hi @zoharHenMicrosoft there are too many services get changed in this pr, and I believe some of them are just format change. I suggest you revert those changes on those services that you do not want to update. We can find another way to fix the formatter CI.

Hi @zoharHenMicrosoft there are too many services get changed in this pr, and I believe some of them are just format change. I suggest you revert those changes on those services that you do not want to update. We can find another way to fix the formatter CI.

done

Hi! any updates? :)

Hi @zoharHenMicrosoft since there is no update for quite a long time, I will close this PR for now. If you would make more update on this PR, please feel free to reopen this then.

Hi @zoharHenMicrosoft since there is no update for quite a long time, I will close this PR for now. If you would make more updates on this PR, please feel free to reopen this then.

please reopen, as I just added a few more changes :) thanks!

@ArcturusZhang Hi! can you reopen this PR, please?

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

the changes in the other PR have been approved by ARM and the only other change here is to rename the api-version. signing off from ARM side on this.

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

Sorry about the delay. and would you please resolve the last comment that @ravbhatnagar just left? Or please let me know you have already resolved that.

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

Sorry about the delay. and would you please resolve the last comment that @ravbhatnagar just left? Or please let me know you have already resolved that.

Hi! can you please clarify what is the issue I should resolve? as we indeed wish to rename this version, and it seems we pass all tests and requirements :). @ravbhatnagar  @ArcturusZhang

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

Sorry about the delay. and would you please resolve the last comment that @ravbhatnagar just left? Or please let me know you have already resolved that.

Hi! can you please clarify what is the issue I should resolve? as we indeed wish to rename this version, and it seems we pass all tests and requirements :). @ravbhatnagar @ArcturusZhang

SOrry about this that I just re-read @ravbhatnagar 's comment and it turns out that I mis-understand his meanings then. I will merge this as soon as the CI passes.

/azp run

authors: ArcturusZhang AutorestCI azuresdkci msftclas ravbhatnagar zoharHenMicrosoft


text:
Added SoftDeleteRetentionInDays,  CustomizedRecoverable and recoverableDays

Latest improvements:
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 have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask tih@microsoft.com (or NullMDR in github) for additional help.

/azp run automation - sdk

Can one of the admins verify this patch?

authors: AutorestCI azuresdkci gdlxm


text:
[Hub Generated] Review request for Microsoft.Security to add version stable/2020-01-01

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run

Hi @nitsi is this PR ready for review? If so, given that you have the permission to edit labels, it would be best to add a WaitForARMReview label.

You have inconsistency enum definitions between here and the severity in the new alerts.json file, which is causing all SDK generation to fail.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

There is another enum called Status is blocking the SDK generation, would you please take a look and provide a fix for this? @nitsi

/azp run automation - sdk

/azp run automation - sdk

Hi @nitsi could you please have a look and resolve the ARM's comments?

Sorry guys there was a priority shift, I'll be back on this PR by Monday EOD

Hi @nitsi any updates?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run

All CI passed, should be good to merge once ARM signed off

@shblum

/azp run automation - sdk

/azp run automation - sdk

@chiragg4u can you take over ARM review on this one also?

Signing off from ARM side.

Adding new APIs requires a new api-version as per the new versioning guidelines. If you need or think this must be added to the existing api-version, please get sign off from Azure API review board. Adrian hall, Johan Stenberg etc. can help

Removing ARM Review label as APIs are fine from ARM standpoint.

Hi @nitsi is this PR ready to merge? This LGTM and should be good to merge. If this is ready to merge, please remove the DoNotMerge label and let me know. Thanks

/azp run automation - sdk

Hi @nitsi do we have any update on this? Please let me know if this is ready to merge

Hi @nitsi do we have any update on this? Please let me know if this is ready to merge

Not yet, we still have a few things to do before:

Tests
Manifest deployment/update

We will give you an update once we are ready

@ArcturusZhang Please marge

authors: ArcturusZhang AutorestCI azuresdkci majastrz nitsi ravbhatnagar yibirnba


text:
Add instructions for upgrading the container

Fixes #2574

/azp run c - client - ci

repo: Azure/azure-sdk-for-c


text:
Expose track2 module name and version for tracing purpose

Feature Request
Expose track2 module name and version for tracing purpose
We need to add module info into trace context. But Module name and module version are not exposed to public.
e.g.
https://github.com/Azure/azure-sdk-for-go/blob/fb9b7a23d7c37f804a0a9850356b1bd1e5af7a83/sdk/resourcemanager/compute/armcompute/constants.go#L12
Do you think if it is feasible to expose those information? Thanks!

The only reason we never exported it in the past was because we didn't think it would be useful. If there's a real need for these to be exported, we can do that.

We should export if we can't find a suitable way to query this at runtime.

@JeffreyRichter Any concerns with exposing these two fields for all modules?

Doesn't our tracing work as-is?
Why do these variables need to be exposed for tracing (assuming it already works)?
Exposing them is not a big deal but I'd still prefer they NOT be exposed.
So, I'd like to understand better what scenario requires them to be exposed.

SDK is a dependency of our library. I need to add this info into log and trace.
But if I enable logging in sdk. It will print too many entries.
I also need to customize user agent header in request. The length limit is too short. I can't add additional version info into UA header.

I don't quite understand.
You are writing a package that depends on it Go sdk and you want to grab our module and version info and use it in your own logging which is not related to the logging infrastructure we have in our sdk?
If your app depended on any other module which did not have constants for the module name and version embedded in it, then what would you do? Most modules do not have these constants and I don't think that just because we do we need to expose them.
I'm hesitant to expose them because we don't guarantee that we'll keep them in future versions of that their content will keep the same format.

Sorry for my poor written English.

You are writing a package that depends on it Go sdk and you want to grab our module and version info and use it in your own logging which is not related to the logging infrastructure we have in our sdk?
Yes. I will print this in our own logger.

If your app depended on any other module which did not have constants for the module name and version embedded in it, then what would you do? Most modules do not have these constants and I don't think that just because we do we need to expose them.

Arm requests will be generated by sdk and apiVersion will be overwritten in our lib. So, it is hard to tell which version of sdk is in use.
We do need module version info in our log so that we can know that if the dependency has been changed.

I'm hesitant to expose them because we don't guarantee that we'll keep them in future versions of that their content will keep the same format.
As long as I can tell which version the lib depends on, That's ok.

You can tell because you build your package with the dependent module versions in your go.mod file.

authors: JeffreyRichter MartinForReal RickWinter jhendrixMSFT

repo: Azure/azure-sdk-for-go


text:
Relative links broken

There are some links here and there, such as [...](/examples) in arm/README.md but those are broken right now. That one should be (/arm/examples) instead (or maybe (./examples), I'm not sure).
Somebody should go through these links and validate them ideally.

@mcardosos Please look into this.

PR sent :3

authors: ahmetalpbalkan garimakhulbe mcardosos


text:
Budgets API is not maintaining case on dictionary keys

Bug Report
Using this SDK.
Budget PUT operation from client logs:
{
  "properties": {
    "amount": "100.65",
    "category": "Cost",
    "filters": {
      "meters": [
        "00000000-0000-0000-0000-000000000000"
      ],
      "resources": [
        "/subscriptions/{subscription-id}/resourceGroups/MYDEVTESTRG/providers/Microsoft.Compute/virtualMachines/MYVM2",
        "/subscriptions/{subscription-id}/resourceGroups/MYDEVTESTRG/providers/Microsoft.Compute/virtualMachines/platformcloudplatformGeneric1"
      ],
      "tags": {
        "CATEGORY": [
          "Dev",
          "Prod"
        ],
        "DEPARTMENT": [
          "engineering",
          "sales"
        ]
      }
    },
    "notifications": {
      "TEST_NOTIFICATION": {
        "enabled": true,
        "operator": "GreaterThan",
        "threshold": "80.12",
        "contactEmails": [
          "andrew.brown@nowhere.com"
        ]
      }
    },
    "timeGrain": "Monthly",
    "timePeriod": {
      "startDate": "2019-08-01T00:00:00Z",
      "endDate": "2022-10-31T00:00:00Z"
    }
  }
}

Immediately followed by GET operation from client logs:
{
  "id": "providers/Microsoft.Management/managementGroups/plat-dev-innovation-1/providers/Microsoft.Consumption/budgets/MyBudget",
  "name": "MyBudget",
  "type": "Microsoft.Consumption/budgets",
  "eTag": "\"1d5491626ce6f97\"",
  "properties": {
    "timePeriod": {
      "startDate": "2019-08-01T00:00:00Z",
      "endDate": "2022-10-31T00:00:00Z"
    },
    "timeGrain": "Monthly",
    "amount": 100.65,
    "currentSpend": {
      "amount": 0.0,
      "unit": "USD"
    },
    "category": "Cost",
    "notifications": {
      "tesT_NOTIFICATION": {
        "enabled": true,
        "operator": "GreaterThan",
        "threshold": 80.1200,
        "contactEmails": [
          "andrew.brown@nowhere.com"
        ],
        "contactRoles": [],
        "contactGroups": [],
        "thresholdType": "Actual"
      }
    },
    "filters": {
      "resourceGroups": [],
      "resources": [
        "/subscriptions/{subscription-id}/resourceGroups/MYDEVTESTRG/providers/Microsoft.Compute/virtualMachines/MYVM2",
        "/subscriptions/{subscription-id}/resourceGroups/MYDEVTESTRG/providers/Microsoft.Compute/virtualMachines/platformcloudplatformGeneric1"
      ],
      "meters": [
        "00000000-0000-0000-0000-000000000000"
      ],
      "tags": {
        "category": [
          "Dev",
          "Prod"
        ],
        "department": [
          "engineering",
          "sales"
        ]
      }
    }
  }
}

Note how the first 3 letters of the notification key have been mutated to lower case and the filter tag keys have been completely mutated.
This breaks state comparison when using tools such as Terraform.

Hi @andysworkshop  I've tagged this so the right person on the team can find it.

authors: andysworkshop loarabia


text:
False Negative 403 on fileServiceClient.WriteRange()

Hello,
Was using your SDK and got weird 403; however file was uploaded successfully.
BlobServiceClient, TableServiceClient did not have this issue.
storage: service returned error: StatusCode=403, ErrorCode=AuthenticationFailed, ErrorMessage=Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:ab1ebe3d-001a-000b-4b37-43efdf000000\nTime:2017-10-12T08:53:02.3784215Z, RequestInitiated=Thu, 12 Oct 2017 08:53:02 GMT, RequestId=ab1ebe3d-001a-000b-4b37-43efdf000000, API Version=, QueryParameterName=, QueryParameterValue="

Thanks!

Hello @kylycht !
How does you code look like? Your code might not be specifying theFileRange correclty:
file.WriteRange(bytes.NewReader(contentBytes), FileRange{End: fileSize - 1}, nil)

hi, @mcardosos
remoteF.WriteRange(f, storage.FileRange{Start: 0, End: uint64(size) - 1}, nil)

@mcardosos
Issue was fixed by passing bytes.NewBuffer, since it was unable to set ContentLength from os.File

Sounds like this was resolved, thanks for the feedback @kylycht

authors: kylycht mcardosos salameer


text:
Release sdk/resourcemanager/devtestlabs/armdevtestlabs v0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armdevtestlabs - ci

/check-enforcer override


text:
Release sdk/resourcemanager/elastic/armelastic v0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armelastic - ci

/check-enforcer override

authors: Alancere ArcturusZhang


text:
Event Grid Sprint 1

Tasks
#12377

[x] Familiarity with Azure
[x] Familiarity with Event Grid
[x] Read service documentation
[x] Review Azure Core libraries
[x] Review existing Event Grid libraries
[x] Review existing Event Grid samples
[x] Make some basic service calls using generated code like create topic, create event subscription, publish event to topic

#12378

[x] Review Event Grid REST API
[x] Familiarity with Java code generation via AutoRest
[x] Create Event Grid project skeleton in the Java repo

#12379

[x] Add unit and integration tests for generated code

Deliverables

[x] Auto-generated REST API code
[ ] Arch Board: Introduction to Event Grid service
[x] Stretch: Pseudo code for Champion scenarios

Related #12376

Thanks @Soreloser2 and @bsiegel for your wonderful work.
Close it now.

authors: YijunXieMS bsiegel

repo: Azure/azure-sdk-for-java


text:
[BUG] SqlQuerySpec datetime inequality returns no results

Describe the bug
When a SqlQuerySpec issues a query containing a datetime string inequality the query returns no results even when it would be expected. Queries which bypass SqlQuerySpec and utilize only a query string return the expected number of results.
Exception or Stack Trace
Add the exception log and stack trace if available
No exception, the query returns zero results.
To Reproduce
Steps to reproduce the behavior:
See Code Snippet.
Code Snippet
Add the code snippet that causes the issue.
A query employing SqlQuerySpec to issues a query containing a datetime string inequality will reproduce the error:
String queryText = "SELECT * FROM ROOT r WHERE r.id = @name AND r.projectStartDate = @projectDate";
List<SqlParameter> paramList = new ArrayList<>();
paramList.add(new SqlParameter("@name", "ContosoInternal")); paramList.add(new SqlParameter("@projectDate", "2018-01-06T19:21:27.0000000Z"));

However, the error will not occur if the query is issued directly as a string bypassing SqlQuerySpec:
"SELECT * FROM ROOT r WHERE r.id = 'ContosoInternal' AND r.projectStartDate = '2018-01-06T19:21:27.0000000Z'";

For reference, here is the JSON datamodel utilized in these tests (the partition key is projectStartDate):
{
    "id": "SannyRicssonEntertainmentProject",
    "projectManager": "Leif Carlson",
    "projectStartDate": "2020-05-05T19:21:27.0000000Z",
    "_rid": "GU1TALwMZZEBAAAAAAAACA==",
    "_self": "dbs/GU1TAA==/colls/GU1TALwMZZE=/docs/GU1TALwMZZEBAAAAAAAACA==/",
    "_etag": "\"0000b800-0000-0700-0000-5f96c6400000\"",
    "_attachments": "attachments/",
    "_ts": 1603716672
}

Expected behavior
The SqlQuerySpec query should perform exactly as the direct query string does.
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Setup (please complete the following information):

OS: Windows
IDE : Intellij
Version of the Library used: 4.8.0

Additional context
This issue was found in the context of testing Spring Data Azure Cosmos DB, which consumes Azure Cosmos DB Java SDK 4.x.x
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x ] Bug Description Added
[ x] Repro Steps Added
[ x] Setup information Added

@anfeldma-ms any updates on this? This has been open for some time so has it been resolved with newer versions of the SDK?