Add support to rotate a single server or loadbalancermux node certificate#546
Open
Add support to rotate a single server or loadbalancermux node certificate#546
Conversation
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
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.
This pull request adds support for performing certificate rotation on specific Load Balancer Mux and Server nodes within the SDN fabric by introducing a new optional
ResourceRefparameter to the relevant cmdlets. The implementation ensures that if aResourceRefis provided, operations are scoped to the specified node; otherwise, all nodes are targeted as before.Enhancements to certificate rotation cmdlets:
ResourceRefparameter to bothStart-SdnMuxCertificateRotationandStart-SdnServerCertificateRotationfunctions, allowing users to specify a single resource (e.g.,/loadBalancerMuxes/{name}or/servers/{name}) for targeted certificate rotation. [1] [2]ResourceRefparameter across all parameter sets. [1] [2]Conditional logic based on
ResourceRef:ResourceRefis provided, otherwise defaulting to all nodes. [1] [2]ResourceRefis used, maintaining compatibility with previous behavior for all-nodes operations. [1] [2]Change type
Checklist: