Repository navigation
conformance: the suite's host connector (Q-P4-9): the http need through busbar's connector to a real local HTTPS far end - #13
Merged
Conversation
…need served by busbar's connector, deliveries reaching a real local HTTPS far end; pinned to busbar lane-p4-fleet-doors 324e30d2b0 - declares.json states the sink's network need (`needs: ["http"]`), the data the fleet render reads. - Rendered by `busbar-release plugin render busbar-export-webhook --tree . --out . --pin 324e30d2b0... 1.6.0` (busbar-release branch p4-conf-host): the pin (.busbar-ref, Cargo.toml, the workflow refs), the host adapter (export-webhook-plugin/tests/support/conformance_host.rs), its dev-dependency rows (busbar-core-connector with test-support, busbar-transport-tcp and -http at busbar's revs), the one-contract [patch] and deny.toml's sources. Cargo.lock re-resolved from busbar's lock at the pin. - tests/conformance.rs adopts the suite's `host:` (the rendered host, with the suite's far end answering HTTP 200 once a whole request is read) and `tls:` (the host's test anchors); the plugin crate takes the host's dev-dependencies; conformance.json's target is the far end (https://localhost:51655/busbar) and `deliver #0` is the dialing step that must resume. Local: fmt, clippy -D warnings, cargo deny, cargo test --workspace and the release conformance run (9/9: the 6 suite arms incl. red_a_networked_door_with_no_connection_table_is_refused, the host's TLS upgrade against the anchors, RED with them withheld, and an http need through the framer); BUSBAR_CONFORMANCE_RED=count fails with "crossing(s), pinned".
…r's source exactly and each transport framer to busbar's lock); re-rendered with busbar-release #162, Cargo.lock re-resolved from busbar's lock at the pin
… TLS front for in-band StartTLS protocols)
# Conflicts: # Cargo.lock
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.
ARCHITECT Q-P4-9 (d) proof. Stacks on #12 (p2-export-door: the published suite adopted). Pinned to busbar lane-p4-fleet-doors 324e30d2b0 (the suite's host seam, deliver on a ticket, core-connector test-support).
needs: ["http"].plugin render busbar-export-webhook --tree . --out . --pin 324e30d2b0725c9dc8538580b691a487b336a954 1.6.0): the pin, the host adapter (tests/support/conformance_host.rs), its dev-dependency rows, the one-contract patch, deny sources. Cargo.lock re-resolved from busbar's lock at the pin.host:(rendered host + far end answering HTTP 200) andtls:(the host's test anchors); conformance.json targets https://localhost:51655/busbar;deliver #0must resume.Do not merge.