-
Notifications
You must be signed in to change notification settings - Fork 4k
[Az.ServiceFabric] Added parameter AutoGeneratedDomainNameLabelScope
to allow customers to initiate migration to public CA cluster certificates in cmdlet New-AzServiceFabricManagedCluster
and Set-AzServiceFabricManagedCluster
#28349
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
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
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 support for the AutoGeneratedDomainNameLabelScope
parameter to enable migration to public CA cluster certificates in Service Fabric managed clusters. The changes also include alphabetical reordering of constructor parameters for consistency.
Key changes:
- Added
AutoGeneratedDomainNameLabelScope
parameter toNew-AzServiceFabricManagedCluster
andSet-AzServiceFabricManagedCluster
cmdlets - Updated constructor parameter ordering to alphabetical in both PSManagedCluster and PSManagedNodeType models
- Updated help documentation to include the new parameter
Reviewed Changes
Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.
Show a summary per file
File | Description |
---|---|
NewAzServiceFabricManagedCluster.cs | Added AutoGeneratedDomainNameLabelScope parameter and implementation |
SetAzServiceFabricManagedCluster.cs | Added AutoGeneratedDomainNameLabelScope parameter and update logic |
PSManagedCluster.cs | Reordered constructor parameters alphabetically and added new property |
PSManagedNodeType.cs | Reordered constructor parameters alphabetically |
New-AzServiceFabricManagedCluster.md | Updated help documentation with new parameter |
Set-AzServiceFabricManagedCluster.md | Updated help documentation with new parameter |
ChangeLog.md | Added changelog entry for the new feature |
src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedCluster.cs
Outdated
Show resolved
Hide resolved
Set-AzServiceFabricManagedClusterApplication
to correctly overwrite existing application upgrade policy when -RecreateApplication
parameter is specified and no other upgrade policy parameters are boundAutoGeneratedDomainNameLabelScope
to allow customers to initiate migration to public CA cluster certificates in cmdlet New-AzServiceFabricManagedCluster
and Set-AzServiceFabricManagedCluster
AutoGeneratedDomainNameLabelScope
to allow customers to initiate migration to public CA cluster certificates in cmdlet New-AzServiceFabricManagedCluster
and Set-AzServiceFabricManagedCluster
AutoGeneratedDomainNameLabelScope
to allow customers to initiate migration to public CA cluster certificates in cmdlet New-AzServiceFabricManagedCluster
and Set-AzServiceFabricManagedCluster
AutoGeneratedDomainNameLabelScope
to allow customers to initiate migration to public CA cluster certificates in cmdlet New-AzServiceFabricManagedCluster
and Set-AzServiceFabricManagedCluster
AutoGeneratedDomainNameLabelScope
to allow customers to initiate migration to public CA cluster certificates in cmdlet New-AzServiceFabricManagedCluster
and Set-AzServiceFabricManagedCluster
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Description
Fixed
Set-AzServiceFabricManagedClusterApplication
to correctly overwrite existing application upgrade policy when-RecreateApplication
parameter is specified and no other upgrade policy parameters are bound.Based on instructions at https://eng.ms/docs/products/azure-service-fabric/how-to/publiccacluster/managed-tls-solution
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.