Manage artifacts and repositories¶

The Registry is where artifact lifecycle work happens: tracking which Workloads run a given artifact, assessing impact before replacing a locked artifact, and confirming that production Workloads reference locked artifacts. For the underlying model—types, lifecycle, repositories, and configuration layering—see Artifact concepts.

Navigate the service artifact page¶

The Service artifact repositories page, accessed from Registry > Services, is the entry point for browsing all of an organization's artifacts. From the list on the resulting Service artifact repositories page, click a row in the Repository column to open its artifact list.

Each repository's list has separate tabs for Locked and Draft artifacts, with Status, Creation date, and Last modified columns. The two statuses differ in how many Workloads each can back:

To locate a specific artifact, use Filters and Search in the top left corner of the page. Filters includes Created by and Tags fields.

Add a new service artifact¶

Artifact creation is API-first: the Console exposes the REST call so you can copy it into a script or terminal and customize the payload. In the top right corner of the Service artifact repositories page, click + Add service artifact to open the Add new artifact panel. The panel shows a copy-ready code example for creating a simple draft artifact.

The example posts a JSON payload to /api/v2/artifacts/ with a Bearer-token header to create an artifact in draft status. The payload supplies the artifact name and description, then defines container topology under spec.containerGroups[].containers[]—image URI, port, the primary flag, environment variables as name/value pairs, an entrypoint command array, and a readiness probe (path, port, initial delay, period, timeout). Adapt the payload to your container before running the request.

Perform artifact actions¶

Each artifact and repository exposes a small set of lifecycle and governance actions. Which actions appear depends on the artifact's current status—the platform hides actions that would conflict with draft or locked rules.

Opening a repository and selecting an artifact opens the artifact detail view, which displays the Assemble tab. From there, the action buttons (Test, Stop, Lock, Deploy) and the actions menu () are available on every tab.

For a service artifact repository, the actions menu () next to the repository name provides the following actions:

For a service artifact, the available action buttons depend on whether it's Draft or Locked:

Manage service artifact configuration¶

The artifact detail view is organized into three tabs, scoped from definition to deployment:

Assemble a service artifact¶

The Assemble tab defines the artifact and groups its components into three sections:

Review containers¶

The Containers section lists every container in the artifact along with its Image URI. Use this section to confirm what the artifact runs before locking or deploying.

環境変数の設定¶

The Environment variables section displays each variable's Name, Type, Value, and Field, with controls to add, edit, or delete.

For when to put values on the artifact vs. on the Workload runtime, see Configuration layering.

Configure probes¶

The Probes section displays the artifact's readiness, liveness, and startup probes. Probes are used to check if the container is running and healthy. The path of a probe is required, and other unfilled fields receive default values.

On the Probes table, click Edit to configure the probe Path, Port, Initial delay (s), Timeout (s), Period (s), and Failure threshold.

View the service artifact info¶

The Info tab displays the artifact's description, Artifact type, Created by information, Last modified date, Artifact repository ID, and Artifact ID. For a draft artifact, click next to the description to update it.

View the Workload and endpoint¶

The Workload tab displays the Workload and endpoint associated with the artifact. Click View detailed info in Console to open the Workload in Console in a new tab.