1 Using kumori.systems Artifacts (public registry)

This tutorial shows how to consume artifacts published under the default public registry selector: kumori.systems/....

Conceptually, it works like any other dependency:

  1. Add a dependency in kumori.mod.json
  2. Download it (kdsl mod download or kdsl mod dep ... --download)
  3. Import a package from that module
  4. Reference the artifact in a service or deployment

1.1 Add a dependency from the public index

Example: add kumori.systems/verdaccio@1.0.0 (this module is used in the CLI tests).

kdsl mod dep kumori.systems/verdaccio@1.0.0 --alias verdaccio --download

Resulting kumori.mod.json entry:

{
  "spec": "kumori/module/v1",
  "module": "kumori.tutorials/uses-public-index",
  "kumori": "0.0.1",
  "version": "0.0.1",
  "requires": [
    {
      "target": "kumori.systems/verdaccio",
      "version": "1.0.0",
      "alias": "verdaccio"
    }
  ]
}

1.2 Import a package and reference an artifact

Once downloaded, you can import one of the module’s packages. With an alias, the import starts with that alias:

import "verdaccio/component"

Then, reference artifacts from that package using package.ArtifactName.

A minimal deployment shape looks like this:

import (
    "verdaccio/component"
)

deployment {
    name       "my-registry"
    artifact   component.Verdaccio
    resilience 1

    config {
        // Fill this based on the artifact interface
    }

    resource {
        // Fill this based on the artifact interface
    }
}

The actual package path (component, service, etc.) and artifact name depend on the specific module you depend on. After downloading, inspect the module sources under your cache location (default: .kumori/mod/) to see what packages/artifacts it exports.

1.3 Registry configuration (what makes kumori.systems special)

  • kumori.systems is the default registry selector, so most users don’t need extra setup.
  • If you want to inspect or add registries manually, see: