How awslabs/edo works
Project type and purpose
• Edo is a Rust-based, next-generation build tool with a CLI front-end and a core library that implements a reproducible, artifact-centric build model.
• It provides four core components—Storage, Source, Environment, Transform—plus a WebAssembly-based plugin system and a Starlark interpreter for configuration.
File structure
• Top-level “crates” directory contains:
• edo-core: core library implementing context, scheduler, storage, source, environment, transform, utilities
• edo-plugin-sdk: SDK for writing plugins in Rust that compile to WASM
• edo-starlark: built-in Starlark interpreter for config
• edo-wit: WIT interface definitions for host/plugin APIs
• edo: CLI binary (cmd/checkout, run, list, etc.)
• plugins/edo-core-plugin: reference plugin implementing common back-ends (local, container, Git, OCI, S3, compose, script)
• docs/components and docs/design.md describe the four core components and plugin system.
• examples demonstrate end-to-end usage invoking the CLI, Starlark config, and plugin behavior.
README for additional insights
• The Architecture section already sketches a linear pipeline: Transform → Environment → Source → Storage, all glued by Plugin System.
• Key technologies: Rust, WebAssembly (WASM), WIT, Starlark, OCI artifact model, container runtimes (Docker/Podman/Finch), S3, Git.
Elements
• Control flow (CLI → Core → Scheduler → Transform → …)
• Data flow (Source → Storage, external fetch/store)
Final advice
• Don’t over-modularize; represent each of the four core components plus orchestration and plugin system as distinct modules.
• External dependencies explicitly.
• Plugin lifecycle (host loading WASM, calling plugin hooks) is obvious.