Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Preannounce removal of *.deps.json files in Az modules #2637

Merged
merged 2 commits into from
Jul 7, 2023
Merged

Preannounce removal of *.deps.json files in Az modules #2637

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8179d0a
Update upcoming-breaking-changes.md
isra-fel Jul 7, 2023
78752f5
Wordsmithing and grammar edits
mikefrobbins Jul 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs-conceptual/azps-10.1.0/upcoming-breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,18 @@ title: Upcoming breaking changes in Azure PowerShell

# Upcoming breaking changes in Azure PowerShell

## General

Beginning with Az version 10.2, Azure PowerShell will no longer include the `*.deps.json` files in
the modules' binary because of two major reasons:

1. The purpose of `*.deps.json` files is to
[guide the default probing of .NET](/dotnet/core/dependency-loading/default-probing#how-are-the-properties-populated).
However, Azure PowerShell never utilized that feature.
1. Some code scanning tools rely on `*.deps.json` files to scan for outdated dependencies, but the
files are not accurate enough because they describe the assemblies that Azure PowerShell requires
rather than what it's shipped with. This inaccuracy caused many false positives to be reported.

## Az.Aks

### `New-AzAksCluster`
Expand Down