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

CLI[Node]: Allow deploying different number network nodes #582

Closed
Tracked by #420
leninmehedy opened this issue Nov 22, 2023 · 2 comments · Fixed by #726
Closed
Tracked by #420

CLI[Node]: Allow deploying different number network nodes #582

leninmehedy opened this issue Nov 22, 2023 · 2 comments · Fixed by #726
Assignees
@leninmehedy
Labels
P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. released
Milestone
v0.20.0

Comments

@leninmehedy
Copy link
Member

leninmehedy commented Nov 22, 2023 •
edited by nathanklick
Loading

Currently, we only support deploying 3 network nodes since we don't have the Gossip and TLS keys for more nodes.

Once we are able to generate Gossip and TLS keys, we need to allow user to select the number of network-nodes.

Related Issues
@leninmehedy leninmehedy moved this to 🔖 Ready in FST Suite Nov 22, 2023
@leninmehedy leninmehedy self-assigned this Nov 22, 2023
@leninmehedy leninmehedy mentioned this issue Nov 22, 2023
Closed
@nathanklick nathanklick added the P1 High priority issue. Required to be completed in the assigned milestone. label Jan 22, 2024
@nathanklick nathanklick added this to the v0.18.0 milestone Jan 22, 2024
@nathanklick nathanklick added P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. and removed P1 High priority issue. Required to be completed in the assigned milestone. labels Jan 22, 2024
@nathanklick nathanklick modified the milestones: v0.18.0, v0.19.0 Jan 22, 2024
@leninmehedy
Copy link
Member Author

Taking this ticket

@leninmehedy leninmehedy moved this from 🔖 Ready to 🏗 In progress in FST Suite Feb 1, 2024
@leninmehedy leninmehedy mentioned this issue Feb 2, 2024
Merged
@leninmehedy leninmehedy moved this from 🏗 In progress to 👀 In review in FST Suite Feb 2, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in FST Suite Feb 3, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.20.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leninmehedy leninmehedy

Labels
P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. released
Projects
FST Suite
Status: ✅ Done
Milestone
v0.20.0
4 participants
@leninmehedy @jeromy-cannon @nathanklick @swirlds-automation