Skip to content

WALL #2 6b: native queue/trigger (remote-cron runner endpoint)#86

Merged
eilandert merged 1 commit into
masterfrom
wall2-6b4-native-queue-trigger
Jun 6, 2026
Merged

WALL #2 6b: native queue/trigger (remote-cron runner endpoint)#86
eilandert merged 1 commit into
masterfrom
wall2-6b4-native-queue-trigger

Conversation

@eilandert
Copy link
Copy Markdown
Owner

Re-land (stacked-merge churn closed #83). Native queue/trigger: Bearer-key (SHA-256) + IP-allowlist gated → ViMbAdmin_QueueRunner::triggerCheck. Last web route off ZF1. Image-validated: 404/401/403/200. See #83 for detail.

Native port of the ZF1 QueueController::triggerAction — the last WEB route still
served by the ZF1 fallback. Unauthenticated machine endpoint: Bearer-key
(SHA-256, constant-time) + source-IP-allowlist gated, then spawns a background
runner via the framework-free ViMbAdmin_QueueRunner::triggerCheck and returns
JSON. Empty queue.runner.key => 404 (disabled). No NATIVE_CONTROLLERS change
(queue already native; the dispatcher invokes the new action) — but this makes
canHandle('/queue/trigger') true, so the native stack now serves it instead of
falling through to ZF1.

Image-validated (vimbadmin:dev): empty key -> 404; no bearer -> 401; bad key ->
403; correct Bearer + allowed IP -> 200 {"triggered":false}. src/ stays free of
the legacy prefix (calls \ViMbAdmin_Net + \ViMbAdmin_QueueRunner, both
framework-free).
@eilandert eilandert merged commit 6b5f308 into master Jun 6, 2026
@eilandert eilandert deleted the wall2-6b4-native-queue-trigger branch June 6, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant