[manjari25]

Why?

The queuepause.Store contract needs OSS implementations so a queue can be paused without a custom backend. Deployers can still supply their own store.

What?

• noop: never pauses a queue. It is the default when nothing is configured.
• file: reads a YAML list of queues with reject_lands and freeze_processing, and re-reads it on every Get, so editing the file pauses or unpauses a queue with no restart.
  • The file must exist and parse at construction, so a mistyped path fails at startup.
  • A later read or parse failure is returned as an error, never treated as not paused.
  • Unknown fields, empty names and duplicate names are errors, so a misspelled switch can't leave a queue unpaused.
• fake: an in-memory store for tests. A test sets a queue's state, changes it while consumers run, and can make every read fail. It is never used in production.

Nothing consumes these stores yet. The gateway wiring follows in the next PR

Test Plan

bazel test //submitqueue/extension/queuepause/...
CI

Issue