Skip to main content

Cosmo Build

To build custom wasmCloud entities like actors, providers or interfaces, cosmo build comes in as a handy tool. One can bring in their own project containing some business logic and build these entities by simply providing the path to the project or its associated wasmcloud.toml file. The built artifact is signed using keys or a user may use their own keys to sign the build.

Usage​

cosmo build -p path/to/wasmcloud.toml

Options​

--config-path (Alias -p) Path to the wasmcloud.toml file or parent folder to use for building

--keys-directory Location of key files for signing. Defaults to $COSMO_KEYS

--issuer (Alias -i) Path to issuer seed key (account). If this flag is not provided, the seed will be sourced from $COSMO_KEYS or generated for you if it cannot be found

--subject (Alias -s) Path to subject seed key (module or service). If this flag is not provided, the seed will be sourced from $COSMO_KEYS or generated for you if it cannot be found

--disable-keygen Disables auto-generation of keys if seed(s) are not provided

--build-only Skip signing the artifact and only use the native toolchain to build