refactor: introduce unified PKI interface for Fabric CA and Vault #295
+2,312
−36
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
- Added a new `pki` package to provide a unified interface for PKI operations. - Deprecated the existing `certs` and `certs_vault` packages, with migration guides included. - Implemented `pkiHelper` for managing PKI operations in the identity, orderer node, and peer controllers. - Updated controllers to utilize the new PKI interface for certificate enrollment and renewal processes. - Added provider registration for both Fabric CA and Vault in the new PKI architecture. Signed-off-by: Aditya Joshi <[email protected]>
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.
pkipackage to provide a unified interface for PKI operations.certsandcerts_vaultpackages, with migration guides included.pkiHelperfor managing PKI operations in the identity, orderer node, and peer controllers.What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation, usage docs, etc.: