[BC] ContainerInstance Module Breaking Changes Announcement Date Update#29146
Open
JunKai-v wants to merge 2 commits intoAzure:mainfrom
Open
[BC] ContainerInstance Module Breaking Changes Announcement Date Update#29146JunKai-v wants to merge 2 commits intoAzure:mainfrom
JunKai-v wants to merge 2 commits intoAzure:mainfrom
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates breaking change announcement dates for the ContainerInstance module, shifting the target version from 15.0.0 to 16.0.0 and the announcement date from November 2025 to May 2026. These changes affect breaking change attributes in multiple cmdlets and update associated metadata files.
Changes:
- Updated breaking change version from 15.0.0 to 16.0.0 and date from "2025/11/03" to "May 2026" across four cmdlets
- Incremented assembly version from 4.1.1 to 4.1.2
- Updated module manifest generation date and Az.Accounts dependency to 5.3.2
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| Az.ContainerInstance.psd1 | Updated generation date, Az.Accounts dependency version, and uncommented ScriptsToProcess/TypesToProcess fields |
| ContainerInstance.sln | Updated project GUID references for AutoRest-generated project |
| generate-info.json | Updated AutoRest generation ID |
| Az.ContainerInstance.md | Updated module GUID in documentation |
| New-AzContainerInstanceObject.ps1 | Updated breaking change attribute with new version and date |
| New-AzContainerInstanceNoDefaultObject.ps1 | Updated breaking change attribute with new version and date |
| New-AzContainerInstanceInitDefinitionObject.ps1 | Updated breaking change attribute with new version and date |
| New-AzContainerGroup.ps1 | Updated breaking change attributes with new version and date |
| AssemblyInfo.cs | Incremented assembly version to 4.1.2 |
| # Generated by: Microsoft Corporation | ||
| # | ||
| # Generated on: 8/27/2025 | ||
| # Generated on: 06-Feb-26 |
There was a problem hiding this comment.
The date format "06-Feb-26" is inconsistent with the convention used throughout the repository. Most modules use either "M/D/YYYY" format (e.g., "1/10/2026") or "MM/DD/YYYY" format (e.g., "8/27/2025") for the "Generated on:" field. This should be changed to match the established convention, such as "2/6/2026" to maintain consistency across the codebase.
| function New-AzContainerInstanceObject { | ||
| [OutputType('Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.Container')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.Container", "15.0.0", "9.0.0", "2025/11/03", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Container", DeprecatedOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol"), NewOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol. This parameter will be changed from single object to 'List'."))] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.Container", "16.0.0", "9.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Container", DeprecatedOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol"), NewOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol. This parameter will be changed from single object to 'List'."))] |
There was a problem hiding this comment.
The date format "May 2026" in the breaking change attribute is inconsistent with the convention used in other modules. Other modules in the repository use "YYYY/MM/DD" format (e.g., "2025/11/03" in CloudService and Databricks modules). For consistency, this should be changed to a format like "2026/05/01" or a specific date in May 2026.
| function New-AzContainerInstanceNoDefaultObject { | ||
| [OutputType('Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.Container')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.Container", "15.0.0", "9.0.0", "2025/11/03", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Container", DeprecatedOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol"), NewOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol. This parameter will be changed from single object to 'List'."))] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.Container", "16.0.0", "9.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Container", DeprecatedOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol"), NewOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, LimitsGpuSku, RequestsGpuSku, ReadinessProbeHttpGetScheme, LivenessProbeHttpGetScheme, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd, Protocol. This parameter will be changed from single object to 'List'."))] |
There was a problem hiding this comment.
The date format "May 2026" in the breaking change attribute is inconsistent with the convention used in other modules. Other modules in the repository use "YYYY/MM/DD" format (e.g., "2025/11/03" in CloudService and Databricks modules). For consistency, this should be changed to a format like "2026/05/01" or a specific date in May 2026.
| function New-AzContainerInstanceInitDefinitionObject { | ||
| [OutputType('Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.InitContainerDefinition')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.InitContainerDefinition", "15.0.0", "9.0.0", "2025/11/03", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.InitContainerDefinition", DeprecatedOutputProperties = ("EnvironmentVariable, InstanceViewEvent, VolumeMount, Command, CapabilityDrop, CapabilityAdd"), NewOutputProperties = ("EnvironmentVariable, InstanceViewEvent, VolumeMount, Command, CapabilityDrop, CapabilityAdd. This parameter will be changed from single object to 'List'."))] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.InitContainerDefinition", "16.0.0", "9.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.InitContainerDefinition", DeprecatedOutputProperties = ("EnvironmentVariable, InstanceViewEvent, VolumeMount, Command, CapabilityDrop, CapabilityAdd"), NewOutputProperties = ("EnvironmentVariable, InstanceViewEvent, VolumeMount, Command, CapabilityDrop, CapabilityAdd. This parameter will be changed from single object to 'List'."))] |
There was a problem hiding this comment.
The date format "May 2026" in the breaking change attribute is inconsistent with the convention used in other modules. Other modules in the repository use "YYYY/MM/DD" format (e.g., "2025/11/03" in CloudService and Databricks modules). For consistency, this should be changed to a format like "2026/05/01" or a specific date in May 2026.
Comment on lines
+27
to
+28
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.Api20240501Preview.IContainerGroup", "16.0.0", "9.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Models.IContainerGroup", DeprecatedOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd"), NewOutputProperties = ("Port, EnvironmentVariable, InstanceViewEvent, LivenessProbeHttpGetHttpHeader, ReadinessProbeHttpGetHttpHeader, VolumeMount, ReadinessProbeExecCommand, Command, CapabilityDrop, LivenessProbeExecCommand, CapabilityAdd. This parameter will be changed from single object to 'List'."))] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ContainerInstance.Runtime.GenericBreakingChangeAttribute("IdentityType will be removed. EnableSystemAssignedIdentity will be used to enable/disable system assigned identity and UserAssignedIdentity will be used to specify user assigned identities.", "16.0.0", "9.0.0", "May 2026")] |
There was a problem hiding this comment.
The date format "May 2026" in the breaking change attributes is inconsistent with the convention used in other modules. Other modules in the repository use "YYYY/MM/DD" format (e.g., "2025/11/03" in CloudService and Databricks modules). For consistency, this should be changed to a format like "2026/05/01" or a specific date in May 2026.
6 tasks
JunKai-v
added
Breaking Change Preannounce
Contributor
Author
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
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.