Alan Chen

`smartmodule/examples` and other repository smartmodules should be built with a consistent `smdk` build artifact instead of cargo directly. One example that goes part way but needs further refinement is: https://github.com/infinyon/fluvio/pull/3997...

- reuse existing tls auth infrastructure if possible (likely possible) - add metadata for edge identity label as part of the certificate

- regular accesses to remote (edge) cluster should not be able to modify mirror topics installed by the home cluster - only the home cluster can change mirror topic configurations

mirroring: audit log and diagnosis

1

- mirroring changes should generate log lines into sc logs - there should be enough information to check for drift/spec version changes

- E2E (1 home and 2 remotes) - bats (optional)

Mapped to `cargo clean`

Allow for e.g. query parameter additions onto ``` # config-example-params.yaml apiVersion: 0.1.0 meta: version: 0.2.5 name: my-http-sink type: http-sink topic: http-sink-topic secrets: - name: AUTHORIZATION_TOKEN http: endpoint: "https://someurl.com${{ record.json.uri_param }}"...

see Rust API https://docs.rs/fluvio/latest/fluvio/consumer/struct.ConsumerConfigExt.html see https://github.com/infinyon/fluvio-client-python/issues/415

[Bug]: Large custom producer settings caused stall on consume

3

**What happened** Producing to fluvio with large record batch settings (10 MiB) can cause stalls on consume. Sample config below: ```rust async fn get_fluvio_producer(fluvio: &Fluvio, topic_name: &str) -> Result {...