This issue will track the progress of the new ZombieNet SDK.
We want to create a new SDK for ZombieNet
that allow users to build more complex use cases and interact with the network in a more flexible and programatic way.
The SDK will provide a set of building blocks
that users can combine in order to spawn and interact (test/query/etc) with the network providing a fluent api to craft different topologies and assertions to the running network. The new SDK
will support the same range of providers
and configurations that can be created in the current version (v1).
We also want to continue supporting the CLI
interface but should be updated to use the SDK
under the hood.
We plan to divide the work phases to. ensure we cover all the requirement and inside each phase in small tasks, covering one of the building blocks and the interaction between them.
Prototype each building block with a clear interface and how to interact with it
We want to integrate the interactions for all building blocks and document the way that they work together.
CLI
and ensure backwards compatibilityRefactor the CLI
module to use the new SDK
under the hood.
native
and podman
providerdocker
providernomad
provider@paritytech/zombienet
npm package to zombienet
. Keep all zombienet modules under @zombienet/*
org (Completed)paths
race
assertionsink! smart contract
supportzombieconfig.json
exists in same dir with zombienet then the config applied in it will override the default configuration of zombienet. E.G if user wants to have as default native
instead of k8s
he can add to .zndls
and network
files.