node-engine client: compose-candidate takes three key forms, built by the client and read by one parser (A-226b)
Builds: design 47 G (G-22 lead answers 2) A-226b; ADR 0593 §7
This commit is contained in:
@@ -1349,7 +1349,7 @@ type ComposeAnswer struct {
|
||||
|
||||
// ComposeCandidateInput is what compose-candidate takes.
|
||||
type ComposeCandidateInput struct {
|
||||
// the key of the indexer's candidate, <group>.<heads hash>
|
||||
// the key of the candidate to compose: a check's candidate in the indexer, <group>.<heads hash>; a branch pipeline's catalog graph revision, <branch>.<revision> (the node-engine reads its entries through mesh-catalog.revision); or a run on request's, run-<id>; built and read by the seat's client (nodeengineclient)
|
||||
Candidate string `json:"candidate"`
|
||||
// also answer the composition input the candidate was composed from, for the sandbox path
|
||||
Input bool `json:"input,omitempty"`
|
||||
|
||||
Reference in New Issue
Block a user