Skip to main content

Cosmo Par

To add new provider archives to your constellation, you can use cosmo par. You may build new archives from your project into .par files and then add these files to the constellation using the Cosmonic UI or the cosmo par command. Following are the available subcommands:

  • create
  • insert

create​

This subcommand enables you to build new provider archives from an existing or new project. It accepts the name, capability contract ID, vendor, architecture you are building for and the path to provider binary as required arguments.

Usage​

cosmo par create --capid=<your-capability-id> --vendor=<vendor-name> --name=<provider-name> --arch=<arch> --binary=/path/to/binary

Options​

--capid (Alias -c) Capability contract ID (e.g. wasmcloud:messaging or wasmcloud:keyvalue)

--output (Alias -o) Specify output format (text or json) [default: text]

--vendor (Alias -v) Vendor string to help identify the publisher of the provider (e.g. Redis, Cassandra, wasmCloud, etc). Not unique

--revision (Alias -r) Monotonically increasing revision number

--version Human friendly version string

--schema (Alias -j) Optional path to a JSON schema describing the link definition specification for this provider

--directory (Alias -d) 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, it will be sourced from $COSMO_KEYS or generated for you if it cannot be found

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

--name (Alias -n) Name of the capability provider

--arch (Alias -a) Architecture of provider binary in format ARCH-OS (e.g. x86_64-linux)

--binary (Alias -b) Path to provider binary for populating the archive

--destination File output destination path

--compress Include a compressed provider archive

--disable-keygen Disables auto-generation of signing keys

insert​

This subcommand enables you to insert the newly created provider archives into your constellation. It accepts the path to the .par or .par.gz file, architecture you are building for and the path to provider binary as required arguments

Usage​

cosmo par insert /path/to/par-file --arch=<arch> --binary=/path/to/binary

Options​

--arch (Alias -a) Architecture of binary in format ARCH-OS (e.g. x86_64-linux)

--output (Alias -o) Specify output format (text or json) [default: text]

--binary (Alias -b) Path to provider binary to insert into archive

--directory (Alias -d) 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, it will be sourced from $COSMO_KEYS or generated for you if it cannot be found

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

--disable-keygen Disables auto-generation of signing keys