You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create authoritative request summaries, exact change URI mappings, and queue receipt projections before publishing accepted Land requests.
Validation: make fmt && make build && make test && make e2e-test
Copy file name to clipboardExpand all lines: submitqueue/entity/request_log.go
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,11 @@ const (
31
31
// RequestStatusUnknown is the unknown sentinel status. It is set by default when the structure is initialized. It should never be seen in the system.
32
32
RequestStatusUnknownRequestStatus=""
33
33
34
-
// RequestStatusAccepted indicates that the request has been accepted by the system. Typically a gateway service will set this status when the land request is received and persisted to the logging database.
34
+
// RequestStatusAccepting is the internal status of a persisted Land receipt that has not yet been published to the processing pipeline.
35
+
// Public read APIs must not expose requests that remain in this status.
36
+
RequestStatusAcceptingRequestStatus="accepting"
37
+
38
+
// RequestStatusAccepted indicates that the request has been published to the processing pipeline.
35
39
RequestStatusAcceptedRequestStatus="accepted"
36
40
37
41
// RequestStatusStarted is the initial status of a request. It corresponds to the RequestStateStarted state and typically set by the orchestrator service when the request is received and persisted to the operating database.
// Record the accepted status in the request log for reconciliation. Once the request materializes as a Request entity, the status might be updated to "new".
118
-
// It is important to record the status before publishing to the queue for processing. It is important to publish straight to the database and not via a entityqueue.
119
-
// Gateway has to stay consistent with the request log.
0 commit comments