Azure Blueprint cmdlets deprecation. #27002
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
️✔️Az.Accounts
|
| Type | Title | Current Coverage | Description |
|---|---|---|---|
| Test Coverage Less Than 50% | 23.08 % | Test coverage for the module cannot be lower than 50%. |
⚠️ - MacOS
| Type | Title | Current Coverage | Description |
|---|---|---|---|
| Test Coverage Less Than 50% | 23.08% | Test coverage for the module cannot be lower than 50%. |
⚠️ PowerShell Core - Windows
| Type | Title | Current Coverage | Description |
|---|---|---|---|
| Test Coverage Less Than 50% | 23.08% | Test coverage for the module cannot be lower than 50%. |
⚠️ Windows PowerShell - Windows
| Type | Title | Current Coverage | Description |
|---|---|---|---|
| Test Coverage Less Than 50% | 23.08% | Test coverage for the module cannot be lower than 50%. |
️✔️Az.Resources
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
YanaXu
reviewed
Jan 14, 2025
| using Microsoft.WindowsAzure.Commands.Utilities.Common; | ||
| using System; | ||
| using System.Management.Automation; | ||
| using static Microsoft.Azure.Commands.Blueprint.Common.BlueprintConstants; | ||
|
|
||
| namespace Microsoft.Azure.Commands.Blueprint.Cmdlets | ||
| { | ||
| [GenericBreakingChangeWithVersion("Blueprints and associated cmdlets are being deprecated with an encouraged migration to Deployments Stacks.", "", "")] |
There was a problem hiding this comment.
Hi @dantedallag, the deprecation date and version should be clear.
There was a problem hiding this comment.
Hello @YanaXu, I will add you to an email thread which led us to leave these blank.
Essentially, we don't have a firm date or version at which these will be removed. We just want to encourage users to move off of them until they are eventually removed sometime most likely in 2026. When we get closer to a firm date/version of removal, we will update these to reflect that.
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
YanaXu
approved these changes
Jan 17, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Jan 17, 2025
* Deprecate the Blueprints cmdlets. * Update Blueprint cmdlets deprecation messages and changelog. * Changing the deprecation message. * Update deprecation version. * Update blueprint version deprecation. --------- Co-authored-by: Dante DG <test>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Azure Blueprint cmdlets are being deprecated as Blueprints as a whole is deprecated. This is an early deprecation though and support will not be removed on the next breaking change release. In the breaking change release before the breaking change release that will remove all of the cmdlets, the "deprecated by" version strings will be updated.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.