Parent
Follows #470 and #471 — nothing in the repo may still reference the blessed
postgres/s3/console param form before this lands, or CI breaks.
What to build
The C++ param declaration, TOML templating, and validation logic for the postgres,
s3, and console blessed destination types is deleted from dc_bridge. The Bridge's
blessed set shrinks to file and vector only; any destinations entry with
type: postgres|s3|console is now handled purely as an unrecognized type (i.e. must go
through custom_config_files passthrough — no special-cased error message for these
three beyond the Bridge's normal unknown-type rejection).
Acceptance criteria
Blocked by
Parent
Follows #470 and #471 — nothing in the repo may still reference the blessed
postgres/s3/console param form before this lands, or CI breaks.
What to build
The C++ param declaration, TOML templating, and validation logic for the
postgres,s3, andconsoleblessed destination types is deleted fromdc_bridge. The Bridge'sblessed set shrinks to
fileandvectoronly; anydestinationsentry withtype: postgres|s3|consoleis now handled purely as an unrecognized type (i.e. must gothrough
custom_config_filespassthrough — no special-cased error message for thesethree beyond the Bridge's normal unknown-type rejection).
Acceptance criteria
postgres/s3/consoleparam declarations, templating, and their dedicatedvalidation branches removed from
dc_bridge(render.cpp, bridge_node.cpp)destinations.md's blessed-set table and Bridge parameter docs updated to showonly
fileandvectoras blessedfuture_work.mdupdated if it references the old 5-type blessed setcolcon testpasses; no remaining reference to the removed code path anywhere inthe repo (docs, demos, deploy params were already migrated in Migrate demos, deploy params, and docs off blessed postgres/s3/console #471)
Blocked by