Remove deprecated build-spec CLI subcommand#12586
Conversation
Migrate callers to export-chain-spec and drop BuildSpecCmd from sc-cli.
|
/cmd prdoc --audience node_dev --bump major |
|
/cmd label T13-deprecation |
…e_dev --bump major'
Keeps omni-node help test passing while build-spec is removed.
|
@Kanasjnr Check out the CI jobs, they are failing because you removed |
I was waiting on @bkontur regarding the CI is failing on zombienet tests because zombienet-orchestrator 0.4.9 still defaults to build-spec for chain spec generation. After removing the subcommand, tests like sync_blocks_from_tip_without_connected_collator and minimal_template_block_production_test fail with unrecognized subcommand 'build-spec'. Options I was thinking was |
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>
Override zombienet chain spec generation in relay and parachain network builders so tests work after removing the build-spec CLI subcommand.
When zombienet omits --chain, ExportChainSpecCmd defaults to "local", but test-parachain's embedded default uses the empty id (as build-spec did).
Zombienet must export a plain chain-spec first so it can customize genesis (para registration, overrides) before converting to raw. Passing --raw up front skipped that step and left paras unregistered.
Map omni-node's default "local" chain id to the empty default used by build-spec, and restore --raw for the substrate-only block_building test.
Match SharedParams/build-spec when --chain is omitted, and drop the temporary local→empty remaps in test-parachain and omni-node.
|
Per-test Once that lands and is released, i can bump the zombienet deps here and delete the per-test overrides @bkchr |
|
@bkontur 👀 |
Summary
build-specCLI subcommand andBuildSpecCmdfromsc-cli.export-chain-spec.Part of #11561