effort towards getting chainspecbuilder into omni-node fix 5567

[seemantaggarwal]

Adding chain-spec-builder as a subcommand into Polkadot omni node

[iulianbarbu]

There is a polkadot-omni-node README we can update so that when referencing building a chain spec, we specify the chain-spec-builder subcommand.

[iulianbarbu]

Do we need to mention the package? Thought chain-spec-builder = { workspace = true } should do it.

[iulianbarbu]

nit: same comment as for ChainSpecBuilder.

[seemantaggarwal]

I agree I can remove this one, I added it as precautionary

[seemantaggarwal]

[ ./target/release/polkadot-omni-node --help
The command-line arguments provided first will be passed to the parachain node, 
and the arguments provided after -- will be passed to the relay chain node. 

Example: 

polkadot-omni-node [parachain-args] -- [relay-chain-args]

Usage: polkadot-omni-node [OPTIONS] [-- <RELAY_CHAIN_ARGS>...]
       polkadot-omni-node <COMMAND>

Commands:
  key                  Key management CLI utilities
  build-spec           Build a chain specification
  check-block          Validate blocks
  export-blocks        Export blocks
  export-state         Export the state of a given block into a chain spec
  import-blocks        Import blocks
  revert               Revert the chain to a previous state
  chain-spec-builder   Subcommand for generating and managing chain specifications
  purge-chain          Remove the whole chain
  export-genesis-head  Export the genesis state of the parachain
  export-genesis-wasm  Export the genesis wasm of the parachain
  benchmark            Sub-commands concerned with benchmarking. The pallet benchmarking moved to the `pallet` sub-command
  help                 Print this message or the help of

I will add the prdoc and resolve conflicts now, for reference tagging @iulianbarbu @skunert

[seemantaggarwal]

./target/debug/polkadot-omni-node chain-spec-builder --help 
Subcommand for generating and managing chain specifications

Usage: polkadot-omni-node chain-spec-builder [OPTIONS] <COMMAND>

Commands:
  create               Create a new chain spec by interacting with the provided runtime wasm blob
  verify               Verifies the provided input chain spec
  update-code          Updates the code in the provided input chain spec
  convert-to-raw       Converts the given chain spec into the raw format
  list-presets         Lists available presets
  display-preset       Displays given preset
  add-code-substitute  Add a code substitute in the chain spec
  help                 Print this message or the help of the given subcommand(s)

Options:
  -c, --chain-spec-path <CHAIN_SPEC_PATH>  The path where the chain spec should be saved [default: ./chain_spec.json]
  -h, --help                               Print help
  -V, --version                            Print version

After suggested changes, updated command @iulianbarbu

[paritytech-workflow-stopper]

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/13463334319
Failed job name: fmt

[bkontur]

Something like this won't look better?

Suggested change

	if let Err(err) = cmd.run() {
	eprintln!("Error executing chain-spec-builder: {}", err);
	return Err(sc_cli::Error::Application(err.into()));
	}
	Ok(())
	cmd.run()
	.map_err(|err| {
	eprintln!("Error executing chain-spec-builder: {}", err)
	Error::Application(err.into())
	)