event-plugin: Replace source enum with metadata field in events plugin
还没有人认领这个 Issue。
评估
调研方向
首先跟踪必需的环境字段 source-kind 是如何配置并添加到发出的事件中的。比较现有的环境和配置文件处理方式,然后在保留事件发出的同时,将该流程替换为支持 meta;当可以通过受支持的配置路径提供元数据,并且不再需要 source-kind 时,即表示完成。
由索引模型根据 Issue 内容生成。
描述
Problem
Right now we have a required env var field source-kind that is related to the LSP architecture. This field is added to an every event emitted and helps to distinguish between different node types within LSP architecture.
Solution
Since we want the plugin to be more generic, we need to get rid from source-kind, however still have an ability to add additional information to an event. Therefore, we'll benefit from a new field called 'meta':
metashould be set via env variables. We can go in both ways of providing meta data:- env variables. We can define an environment variable which would receive metadata as a key-value string. e.g. this could be in JSON format, something like
EVENT_PLUGIN_META='{"source_kind": "gateway"}'; - config file. We can have a config file (e.g.
.toml) which would contain an information. That's might suit us well since we already have a config file; - apply both variants;
- env variables. We can define an environment variable which would receive metadata as a key-value string. e.g. this could be in JSON format, something like
- the flow should be the same as it was introduced for
source-kind.
- 主要语言
- Rust
- 星标
- 3
- 派生
- 0
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 2
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
Blockstream/cln-plugins 的其他 Issue
-
难度 5/5 一周以上 新手友好度 45/100
Blockstream/cln-plugins#11 ·
查看 Blockstream/cln-plugins 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
BurntSushi/jiff#653 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
ZcashFoundation/zeeder#106 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
oxidize-rb/rb-sys#807 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
-
todo:ticket
难度 2/5 1-2 天 新手友好度 74/100