feat: introduce the CLI and build workflows

[vcastellm]

This is the first PR introducing the CLI to handle configuration and execution of the different components of the system. In this PoC of the CLI it's only capable of running cdk-node as a subprocess and accept 2 configuration files:

1. The genesis file
2. The node-config file

Also introduce the necessary workflows to build and release docker images to docker repositories compiling and including these elements.

e2e-testing

I've simplified a lot here, if we're testing in local, it's assumed that the developer will have a correct environment running, it's opinionated in the sense that it's required to have kurtosis-cdk installed and checked-out on the version you want to try. Similar to having docker installed on your system.

Also, there are a lot of defaults now so we don't need to set them.

Reviewer: @goran-ethernal

[goran-ethernal]

If I disregard the rust files, since I am not in rust yet (and I know you just pushed some base work to continue future work), this looks good to me.

[muursh]

I don't know if I need to do something special to build this code, not being familiar with the existing code at all but cargo check or cargo build gives me the following error

error: failed to run custom build command for `cdk v0.1.0 (/Users/ben/dev/cdk/crates/cdk)`

Caused by:
  process didn't exit successfully: `/Users/ben/dev/cdk/target/release/build/cdk-b8965ac9ee75bf2c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=*.go

  --- stderr
  thread 'main' panicked at crates/cdk/build.rs:29:10:
  Failed to execute make command: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...`

Either there's an issue or I need some build instructions :)

[vcastellm]

@begmaroman the base image now is based on Debian so we need to use golang default image that it's based on debian instead of alpine, binaries are not compatible because the build toolchain is different between them.

[vcastellm]

I don't know if I need to do something special to build this code, not being familiar with the existing code at all but cargo check or cargo build gives me the following error

error: failed to run custom build command for `cdk v0.1.0 (/Users/ben/dev/cdk/crates/cdk)`

Caused by:
  process didn't exit successfully: `/Users/ben/dev/cdk/target/release/build/cdk-b8965ac9ee75bf2c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=*.go

  --- stderr
  thread 'main' panicked at crates/cdk/build.rs:29:10:
  Failed to execute make command: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...`

Either there's an issue or I need some build instructions :)

Yes, some build instructions are needed, but basically it tries to build go code first using a cargo buildscript, so it has the cdk-node binary available.

Could it be that you don't have Go build toolchain installed?

[muursh]

I don't know if I need to do something special to build this code, not being familiar with the existing code at all but cargo check or cargo build gives me the following error

error: failed to run custom build command for `cdk v0.1.0 (/Users/ben/dev/cdk/crates/cdk)`

Caused by:
  process didn't exit successfully: `/Users/ben/dev/cdk/target/release/build/cdk-b8965ac9ee75bf2c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=*.go

  --- stderr
  thread 'main' panicked at crates/cdk/build.rs:29:10:
  Failed to execute make command: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...`

Either there's an issue or I need some build instructions :)

Yes, some build instructions are needed, but basically it tries to build go code first using a cargo buildscript, so it has the cdk-node binary available.

Could it be that you don't have Go build toolchain installed?

Go is installed. v1.22.5 to be specific

[vcastellm]

I don't know if I need to do something special to build this code, not being familiar with the existing code at all but cargo check or cargo build gives me the following error

error: failed to run custom build command for `cdk v0.1.0 (/Users/ben/dev/cdk/crates/cdk)`

Caused by:
  process didn't exit successfully: `/Users/ben/dev/cdk/target/release/build/cdk-b8965ac9ee75bf2c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=*.go

  --- stderr
  thread 'main' panicked at crates/cdk/build.rs:29:10:
  Failed to execute make command: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...`

Either there's an issue or I need some build instructions :)

Yes, some build instructions are needed, but basically it tries to build go code first using a cargo buildscript, so it has the cdk-node binary available.
Could it be that you don't have Go build toolchain installed?

Go is installed. v1.22.5 to be specific

Issue should be fixed now @muursh, can you try again?

[muursh]

I don't know if I need to do something special to build this code, not being familiar with the existing code at all but cargo check or cargo build gives me the following error

error: failed to run custom build command for `cdk v0.1.0 (/Users/ben/dev/cdk/crates/cdk)`

Caused by:
  process didn't exit successfully: `/Users/ben/dev/cdk/target/release/build/cdk-b8965ac9ee75bf2c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=*.go

  --- stderr
  thread 'main' panicked at crates/cdk/build.rs:29:10:
  Failed to execute make command: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...`

Either there's an issue or I need some build instructions :)

Yes, some build instructions are needed, but basically it tries to build go code first using a cargo buildscript, so it has the cdk-node binary available.
Could it be that you don't have Go build toolchain installed?

Go is installed. v1.22.5 to be specific

Issue should be fixed now @muursh, can you try again?

Yep builds now. I'll aim to review today/tomorrow

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 Security Hotspots
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud