Az.Support breaking change announcement

[grhuangmsft]

Description

Add breaking change warning messages for Az.Support powershell module for the following scenarios:

• Added breaking change warning messages for cmdlet deprecation
  • New-AzSupportContactProfileObject
• Added breaking change warning messages for cmdlet rename
  • Get-AzSupportTicketCommunication
  • New-AzSupportTicketCommunication
• Added breaking change warning messages for parameter name and/or structure changes
  • Get-AzSupportService
  • Get-AzSupportProblemClassification
  • Get-AzSupportTicketCommunication
  • Get-AzSupportTicket
  • New-AzSupportTicket
  • Update-AzSupportTicket
• Added breaking change warning messages for output property name and/or structure changes
  • Get-AzSupportService
  • Get-AzSupportTicket
  • New-AzSupportTicket
  • Update-AzSupportTicket
• Added breaking change warning messages for new required parameters
  • New-AzSupportTicket
• Added breaking change warning messages for removed parameters
  • Get-AzSupportTicket
  • Get-AzSupportTicketCommunication
  • New-AzSupportTicket
• Added breaking change warning message for removal of pipe parameter set for list/new
  • New-AzSupportTicketCommunication
  • Get-AzSupportProblemClassification
  • Get-AzSupportTicketCommunication
• Added breaking change warning message for Get-AzSupportTicket retrieving tickets from the past week if no other parameters are specified
  • Get-AzSupportTicket

Mandatory Checklist

• Please choose the target release of Azure PowerShell

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • N/A

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Az.Support

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Signature Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️File Change Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️UX Metadata Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Test

️✔️PowerShell Core - Linux

️✔️PowerShell Core - MacOS

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

[vidai-msft]

LGTM

[vidai-msft]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).