-
Notifications
You must be signed in to change notification settings - Fork 4k
[Az.HealthcareApis] The code base is going to be refactored, the following cmdlet adds a BreakingChange announcement #28368
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.
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
base: main
Are you sure you want to change the base?
Conversation
…owing cmdlet adds a BreakingChange announcement
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
To the author of the pull request, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds breaking change announcements to the Az.HealthcareApis module to inform users of upcoming code base refactoring. The changes prepare for future modifications that will affect cmdlet parameters and output types.
- Updates changelog to announce breaking changes for 15 healthcare cmdlets
- Adds breaking change attributes to PowerShell cmdlet files for proper deprecation warnings
- Updates module dependencies and configuration files for the refactoring
Reviewed Changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 1 comment.
Show a summary per file
File | Description |
---|---|
src/HealthcareApis/HealthcareApis/ChangeLog.md | Adds comprehensive list of cmdlets that will have breaking changes |
src/HealthcareApis/HealthcareApis/Az.HealthcareApis.psd1 | Updates module dependency version and formatting configurations |
src/HealthcareApis/HealthcareApis.sln | Restructures solution file with new project configurations |
src/HealthcareApis/HealthcareApis.Autorest/README.md | Adds breaking change configuration directives for autorest generation |
Multiple cmdlet files | Adds breaking change attributes to New-Az* cmdlets for proper deprecation notices |
Various support files | Updates generated files and documentation with new GUIDs and assembly info |
- CorConfigurationHeader | ||
- IdentityType | ||
- IdentityUserAssignedIdentity | ||
change-description: (1)The types of the properties 'PrivateEndpointConnection' and 'AuthenticationConfigurationAudience' will be changed from single object to 'List'. (2)IdentityType will be removed. EnableSystemAssignedIdentity will be used to enable/disable system assigned identity and UserAssignedIdentity will be used to specify user assigned identities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The word 'AuthenticationConfigurationAudience' is mentioned in the change description for FhirService but this property is not listed in the deprecated-output-properties or new-output-properties sections above. This appears to be copied from the DicomService section where this property is relevant.
change-description: (1)The types of the properties 'PrivateEndpointConnection' and 'AuthenticationConfigurationAudience' will be changed from single object to 'List'. (2)IdentityType will be removed. EnableSystemAssignedIdentity will be used to enable/disable system assigned identity and UserAssignedIdentity will be used to specify user assigned identities. | |
change-description: (1)The type of the property 'PrivateEndpointConnection' will be changed from single object to 'List'. (2)IdentityType will be removed. EnableSystemAssignedIdentity will be used to enable/disable system assigned identity and UserAssignedIdentity will be used to specify user assigned identities. |
Copilot uses AI. Check for mistakes.
#28317
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.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.