Connections & Artifacts
Connections and artifacts enable type-safe composition of infrastructure components in Massdriver.
Key concepts​
- Artifacts are the outputs a bundle produces (e.g., database connection details, cluster credentials)
- Connections are the inputs a bundle consumes from other bundles' artifacts
- Artifact Definitions are the schemas that define the contract between bundles
How it works​
When you connect bundles on the canvas, Massdriver validates that:
- The artifact type matches the connection's expected type
- The artifact data conforms to the artifact definition schema
- Any additional constraints (version, region) are satisfied
This validation happens at design time, preventing incompatible infrastructure from being deployed.
In this section​
- Artifact Definition Specification - Complete reference for defining artifact schemas
Related documentation​
- Concepts: Artifacts & Definitions - Conceptual overview
- Bundle YAML: connections - Connection schema reference
- Bundle YAML: artifacts - Artifact output reference
- Artifact Definitions Repository - Standard artifact types