Some checks failed
Run Check Script / check (pull_request) Failing after 2m3s
29 lines
1.1 KiB
Rust
29 lines
1.1 KiB
Rust
//! In-cluster end-to-end harness for the harmony fleet stack.
|
|
//!
|
|
//! Brings up the fleet stack ([`FleetNatsScore`] +
|
|
//! [`FleetAgentScore`]) in a fresh per-bring-up k3d namespace and
|
|
//! hands the test a connected NATS admin client + the device ids the
|
|
//! agents are running under. Bring-up is shared across tests in the
|
|
//! same binary (`Stack::shared`); the cluster itself is reused across
|
|
//! runs.
|
|
//!
|
|
//! Per ADR-023, the harness composes the same `*Score` types the
|
|
//! production CLI uses. It does **not** build manifests itself.
|
|
//!
|
|
//! [`FleetNatsScore`]: harmony_fleet_deploy::FleetNatsScore
|
|
//! [`FleetAgentScore`]: harmony_fleet_deploy::FleetAgentScore
|
|
|
|
mod images;
|
|
mod kv_admin;
|
|
mod namespace;
|
|
mod stack;
|
|
pub mod vm;
|
|
|
|
pub use images::{AGENT_IMAGE_TAG, Images, build_and_sideload};
|
|
pub use kv_admin::{AdminKv, AdminKvError, PhaseExpectation};
|
|
pub use namespace::{ENV_KEEP_NAMESPACE, NamespaceGuard};
|
|
pub use stack::{
|
|
AuthMode, BringUpError, CLUSTER_NAME, NATS_NODE_PORT, Stack, StackOptions, shared_stack,
|
|
};
|
|
pub use vm::{VmBringUpError, VmDevice, VmStack, VmStackOptions, shared_vm_stack};
|