Documentation
¶
Overview ¶
Package landconflictsignal consumes merge-conflict results from Runway's signal queue, correlates them to the land request by the echoed id, and either advances the request to the batch stage (landable) or fails it (conflicted). Unlike buildsignal it is purely result-driven — Runway pushes the result, so there is no poll loop or self-reschedule.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Controller ¶
type Controller struct {
// contains filtered or unexported fields
}
Controller handles landconflictsignal queue messages. Implements consumer.Controller.
func NewController ¶
func NewController( logger *zap.SugaredLogger, scope tally.Scope, stores storage.Factory, registry consumer.TopicRegistry, topicKey consumer.TopicKey, consumerGroup string, ) *Controller
NewController creates a new landconflictsignal controller for the orchestrator.
func (*Controller) ConsumerGroup ¶
func (c *Controller) ConsumerGroup() string
ConsumerGroup returns the consumer group for offset tracking.
func (*Controller) Name ¶
func (c *Controller) Name() string
Name returns the controller name for logging and metrics.
func (*Controller) Process ¶
Process consumes a runway check result and advances or fails the request. Returns nil to ack, or error to nack/reject.
A not-landable verdict is an expected outcome of the check, not a failure: the request is driven to terminal Error inline and the message is acked. Only infrastructure faults — deserialize, storage, the terminal transition, and the batch publish — return an error and reject to the DLQ, where the request is reconciled to Error.
func (*Controller) TopicKey ¶
func (c *Controller) TopicKey() consumer.TopicKey
TopicKey returns the topic key this controller subscribes to.
Source Files