-
Notifications
You must be signed in to change notification settings - Fork 551
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
feat: int in-place testnet creation #4297
feat: int in-place testnet creation #4297
Conversation
From v28.5.1 and this commit I tried creating a chain called "testchain" and running it with 4 nodes then stopping it. Executing the command and get the expected results:
Chain created from ignite (including node initialization script): testchain |
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.
Good start, but we are missing a few things:
- There are too many hard-coded addresses, we should make use of ignite config for that
- We should create an
ignite testnet
command to launch this given a path. Meaning the actualappd
commands takes many arguments thatignite testnet in-place
is passing properly based on the config.yml. Think of it as a wrapper.
Thank you for taking the time to review and provide feedback! Your input is invaluable and helps me improve.
|
I have made the updates and look forward to receiving your review again @julienrbrt |
Sorry I'm still lacking, you don't need to review it right away. |
updates add command testnet inplace
Co-authored-by: Danilo Pantani <[email protected]>
f5d1224
to
5d09ef5
Compare
I have completed the requirements in this PR and am ready to merge. I am happy to contribute to the project and hope these changes will bring value to the product. |
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.
Can you verify if nothing break in ignite s chain foo --minimal
? Looks like it does: TestGenerateAnAppMinimal
For chains created from --minimal, the slashing module is not used, so app.SlashingKeeper does not exist. This can be solved in two ways:
I will solve it with way 2 because it comes from this PR. |
We should keep it, we can just have a condition in the template. |
Thanks @julienrbrt, looks great. |
I have completed the required work. When can I receive the reward? How will the reward be received? |
Yes, congratulations! I will send someone your way to arrange that. |
Thanks! I am glad to have completed the work. For convenience of communication, you can email me at [email protected]. |
(cherry picked from commit f7618d3) # Conflicts: # docs/docs/03-CLI-Commands/01-cli-commands.md # ignite/pkg/chaincmd/chaincmd.go
* feat: int in-place testnet creation (#4297) (cherry picked from commit f7618d3) # Conflicts: # docs/docs/03-CLI-Commands/01-cli-commands.md # ignite/pkg/chaincmd/chaincmd.go * updates * cl * re * consumer handling --------- Co-authored-by: Duong NV | Decentrio <[email protected]> Co-authored-by: Julien Robert <[email protected]>
close: #4244
This PR includes additional in-place-testnet command