Background
Design doc 4719 established the three-module structure (alloy, extension/alloyengine, collector) and a dependency-replacements.yaml DSL that fans replace directives across them. Maintaining three go.mod files in sync plus the DSL has measurable ongoing overhead, which #6131 currently proposes to automate around.
Question
Does extension/alloyengine need its own go.mod at all, given that it is intrinsically coupled to the Alloy runtime via flowcmd?
Proposal
Design PR will be linked when opened.
Related: #6131
Background
Design doc 4719 established the three-module structure (alloy,
extension/alloyengine,collector) and adependency-replacements.yamlDSL that fans replace directives across them. Maintaining threego.modfiles in sync plus the DSL has measurable ongoing overhead, which #6131 currently proposes to automate around.Question
Does
extension/alloyengineneed its owngo.modat all, given that it is intrinsically coupled to the Alloy runtime viaflowcmd?Proposal
Design PR will be linked when opened.
Related: #6131