The connector-trusted trust mode is the dev-only escape hatch and
must require both -trust=connector-trusted *and*
-dev.connector_trusted_ack. The latter is intentionally awkward to
flip so an operator cannot disable catalog validation by accident.
Add unit tests covering: default ok, port range, missing filer
addresses, connector-trusted without ack rejected, connector-trusted
with ack accepted, unknown trust modes rejected, and that the error
message names the ack flag so the operator knows how to proceed.
Add weed/parquet_pushdown/daemon, the host process for the
SeaweedParquetPushdown service:
- Config carries bind ip/port, filer addresses, trust mode, and the
ConnectorTrustedAck flag that gates the dev-only connector-trusted
trust mode (default refuses it; explicit ack required).
- filerClient probes the filer with GetFilerConfiguration at startup
so bad endpoints fail fast, mirroring the iam command's pattern.
Bounded by a 60s timeout; later milestones use the same client to
read Parquet data and side-index blobs.
- server.go wires it together: load TLS, probe filer, build the
Service, listen on (host, localhost) gRPC ports, register the
service + reflection on each, install grace.OnInterrupt for
GracefulStop, and Serve.
Run() returns an error so the calling weed pushdown command can
report startup failures instead of glog.Fatalf.
Chris Lu