workspace

Orchestrate cross-charm deployment planning and testing from a workspace manifest.

1|Updated Feb 8, 2026

Search Tags:#workflow #workspace #manifest #charm #integration-testing #juju #cross-charm

Ready to run

npx skills add https://github.com/tonyandrewmeyer/cantrip --skill workspace-tonyandrewmeyer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace
Source: https://github.com/tonyandrewmeyer/cantrip/tree/main/src/cantrip/skills/workspace
Command: npx skills add https://github.com/tonyandrewmeyer/cantrip --skill workspace-tonyandrewmeyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across multiple related Juju charms can be error-prone and time-consuming without a structured runtime to manage manifests, cross-charm relations, and end-to-end testing.

Core Features & Use Cases

Workspace manifests (workspace: name, charms, relations, and optional shared_config) enable a single consolidated view of a multi-charm deployment.
Workspace awareness through workspace_info that reveals charm paths and cross-charm topology, accelerating planning and verification.
Coordinated deployment workflows (deploy, relate, and test across multiple charms) without creating and maintaining deprecated bundles.
End-to-end testing support by colocating Jubilant-style tests at workspace level or per charm.

Quick Start

Ask Cantrip to load the workspace manifest, view the cross-charm layout, and plan tasks across charms.

Frequently Asked Questions about workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate deployment and relations across multiple related Juju charms?▼

Coordinating multiple related Juju charms uses a workspace manifest to define charms, cross-charm relations, and shared config in a single consolidated view. This structured runtime manages deployment planning and end-to-end testing without maintaining deprecated bundles.

What is the best way to run Jubilant integration tests across multiple charms?▼

Running Jubilant integration tests across multiple charms is supported by colocating tests at the workspace level or per charm. The workspace orchestrates these end-to-end tests by interpreting the manifest to validate cross-charm relations and coordinated deploy workflows.

How do I define cross-charm relations for a multi-charm Juju deployment?▼

Defining cross-charm relations requires specifying them within a workspace manifest. The manifest schema validation ensures the relations design is correct, and workspace_info reveals charm paths and cross-charm topology to accelerate planning and verification.

Do I need a deprecated Juju bundle to deploy and test related charms together?▼

Deprecated Juju bundles are not needed to deploy and test related charms together. A workspace manifest provides coordinated deployment workflows, replacing bundles by orchestrating deploy, relate, and test actions across multiple charms.

Can I use a shared configuration across multiple Juju charms during coordinated deployment?▼

Shared configuration across multiple Juju charms is supported during coordinated deployment. The workspace manifest schema includes an optional shared_config field, allowing a single consolidated configuration view for the multi-charm deployment.

What is a workspace manifest used for in cross-charm integration testing?▼

A workspace manifest is used in cross-charm integration testing to provide a single consolidated view of a multi-charm deployment. It defines the workspace name, charms, relations, and shared config, enabling schema validation and coordinated Jubilant test execution.