Repository navigation
export-webhook: the door states ready, so a refused target is named at boot, as 1.5.5 named it when the sink was configured - #15
Merged
Conversation
… at boot, as 1.5.5 named it when the sink was configured The host's verdict on the target was first asked on the first delivery. Under a cell that serves one request and reads the log 500 ms later, no batch had reached the plugin, so nothing was logged. 1.5.5 refused the target at configuration (`push_target`). The door now states the mechanism's optional `ready` (`abi::mechanism::lifecycle` READY, ARCHITECT 2026-10-02 "discovery at boot"). The host calls it after `open`, before the instance serves (busbar's export axis, coordinator ruling G2), and it asks the verdict there, once. A refusal raises BUSBAR-7070 at ERROR into the instance's plugin log, in 1.5.5's words when it is the https:// rule. It never refuses the boot: the instance is disabled and its siblings serve, as in 1.5.5. Test: ready_asks_the_verdict_at_boot_and_never_refuses_it (host tables with no connector: one BUSBAR-7070 at ERROR, Ok, and nothing asked again at the first delivery).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
busbar row 86, Q-B(1) G2 (coordinator ruling 2026-10-07). Pairs with busbar#558, where the export axis awaits
readyon the open that delivers.The door now states the mechanism's optional
ready(lifecycle: life(Webhook, ready)).Life::readyasks the host's verdict on the target once, via the existingadmitted(), so a refused target raises BUSBAR-7070 at boot, at ERROR, in the instance's plugin log, and in 1.5.5's words when the refusal is the https:// rule (#14). It answers Ok: the boot proceeds with the sink disabled and its siblings serving, as in 1.5.5. Settings that did not parse are the configuration's refusal, not this one's.Proof
ready_asks_the_verdict_at_boot_and_never_refuses_it, over host tables with no connector: one BUSBAR-7070 at ERROR, Ok, and nothing asked again at the first delivery.clippy -D warningsand fmt are clean.export|request-log-webhook|loopback-refused.logs/plugins/export.wh.logholds, written before the listeners bind:2026-10-07T10:52:38Z ERROR export.wh export busbar_export_webhook: observability.request_log_webhook_url must be an https:// URL (got 'http://127.0.0.1:56399/sidecar'); disabling this webhook exporter diag=BUSBAR-7070No byte reached the sidecar.