-
Notifications
You must be signed in to change notification settings - Fork 91
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
Add onboard_as_parachain flag to parachain options #886
Conversation
Co-authored-by: Nikos Kontakis <wirednkod@gmail.com>
Not really sure why the lint jobs are failing in CI. Not getting the same error locally when running |
Can you try running inside |
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.
lgtm
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.
Thanks @antonva!! looks good, a couple of comment mostly about using camelCase in naming and the default value.
Thanks!
Co-authored-by: Javier Viola <javier@parity.io>
Co-authored-by: Javier Viola <javier@parity.io>
Co-authored-by: Javier Viola <javier@parity.io>
Co-authored-by: Javier Viola <javier@parity.io>
Co-authored-by: Loris Moulin <45130584+l0r1s@users.noreply.github.com>
Merged, thanks @antonva! |
Wonderful, thanks for the help! |
This option effectively exposes the
parachain
boolean parameter fromparaSudoWrapper.sudoScheduleParaInitialize
. Exposing the option allows Zombienet to provision parathreads.The default behaviour remains the same but a parachain defined with
onboard_as_parachain = false
will register the para without upgrading/onboarding it to the parachain lifecycle.Example: