Pre-filing checklist
Component(s)
Rust OTAP dataflow (rust/otap-dataflow/)
Is your feature request related to a problem?
Description:
As per the comment from @lquerel here.
Some engine entrypoints currently need explicit bootstrap code before startup, for example installing the rustls crypto provider. That works, but it leaks low-level setup details into binaries, examples, and tests, and makes startup requirements easier to miss or duplicate.
It would be good to have a more ergonomic way to handle this kind of common initialization in one place. As mentioned in PR discussion, this could be a small prelude/bootstrap function, or possibly an attribute macro such as #[engine::main], so callers do not need to remember and repeat the same setup manually.
This issue is to track improving that startup experience and reducing bootstrap boilerplate around engine entrypoints.
Proposed Solution
As mentioned in the description.
Alternatives Considered
None
Additional Context
None
Pre-filing checklist
Component(s)
Rust OTAP dataflow (rust/otap-dataflow/)
Is your feature request related to a problem?
Description:
As per the comment from @lquerel here.
Some engine entrypoints currently need explicit bootstrap code before startup, for example installing the rustls crypto provider. That works, but it leaks low-level setup details into binaries, examples, and tests, and makes startup requirements easier to miss or duplicate.
It would be good to have a more ergonomic way to handle this kind of common initialization in one place. As mentioned in PR discussion, this could be a small prelude/bootstrap function, or possibly an attribute macro such as
#[engine::main], so callers do not need to remember and repeat the same setup manually.This issue is to track improving that startup experience and reducing bootstrap boilerplate around engine entrypoints.
Proposed Solution
As mentioned in the description.
Alternatives Considered
None
Additional Context
None