workspace

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.

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.

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.

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.

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.

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.