Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Addition of new peer org shouldn’t have a dependency on the orderer. #2534

Open
adityajoshi12 opened this issue Mar 28, 2024 · 1 comment
Open

Addition of new peer org shouldn’t have a dependency on the orderer. #2534

adityajoshi12 opened this issue Mar 28, 2024 · 1 comment
Labels
enhancement New feature or request fabric Related to the Hyperledger Fabric DLT Platform

Comments

@adityajoshi12
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Addition of new peer org shouldn’t have a dependency on the orderer (fabric 2.5) since the channel creation is an independent operation.

Describe the solution you'd like
Users should be able to bootstrap a new org without orderer details in the network.yaml.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Fabric 2.5
@adityajoshi12 adityajoshi12 added enhancement New feature or request fabric Related to the Hyperledger Fabric DLT Platform labels Mar 28, 2024
@suvajit-sarkar
Copy link
Contributor

Revisit once the standalone helm chart for fabric is complete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request fabric Related to the Hyperledger Fabric DLT Platform
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adityajoshi12 @suvajit-sarkar