ParthibanRajasekaran commented on issue #4322: URL: https://github.com/apache/iggy/issues/4322#issuecomment-5888913757
Thanks, @hubcio. These are helpful questions. 1. For connectors, I was thinking we could replace `#[tokio::main]` with a synchronous `main`. It would parse `Args` and handle `--list-config-env-vars` first, then build Tokio and run the existing async path only for normal startup. MCP could follow the same pattern, while the server already parses before creating its executor. 2. I don’t think we can safely reconstruct templates from the expanded mappings because literal numbers and generated indexes are indistinguishable, and the limits have been lost. Instead, we could have `ConfigEnv` generate compact template metadata from the same fields and attributes it already processes. This would preserve `<N>` and `max_elements` while leaving the existing mappings and parsing unchanged. Connector `<KEY>` and plugin `<FIELD>` templates could then use the existing local-provider naming rules. The Kafka gateway would remain out of scope. Does this approach align with what you had in mind? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
