Skip to content

Basic .csmrc parsing - #4

Merged
relrod merged 2 commits into
Checkmk:mainfrom
relrod:csmrc
Oct 29, 2025
Merged

Basic .csmrc parsing#4
relrod merged 2 commits into
Checkmk:mainfrom
relrod:csmrc

Conversation

@relrod

@relrod relrod commented Oct 29, 2025

Copy link
Copy Markdown
Member

We rely here on serde_yaml_ng, which is a fork of serde_yaml that
seems at least somewhat actively maintained and used. The benefit here
is that we get easy deserialization into Rust types (which we wouldn't
get with something like yaml_rust2 which just gives an AST). The
disadvantage is that we're depending on a library that I wish had more
community backing like the original serde_yaml did.

The alternative here would probably be foregoing YAML entirely and using
TOML instead, but it seems the rest of the Robotmk ecosystem uses YAML,
so it is probably best to remain consistent here.

@relrod
relrod force-pushed the csmrc branch 2 times, most recently from f8c15f8 to 4f49f8c Compare October 29, 2025 14:09
We rely here on `serde_yaml_ng`, which is a fork of `serde_yaml` that
seems at least somewhat actively maintained and used. The benefit here
is that we get easy deserialization into Rust types (which we wouldn't
get with something like `yaml_rust2` which just gives an AST). The
disadvantage is that we're depending on a library that I wish had more
community backing like the original `serde_yaml` did.

The alternative here would probably be foregoing YAML entirely and using
TOML instead, but it seems the rest of the Robotmk ecosystem uses YAML,
so it is probably best to remain consistent here.
@jherbel

jherbel commented Oct 29, 2025

Copy link
Copy Markdown
Collaborator

We rely here on serde_yaml_ng, which is a fork of serde_yaml that seems at least somewhat actively maintained and used. The benefit here is that we get easy deserialization into Rust types (which we wouldn't get with something like yaml_rust2 which just gives an AST). The disadvantage is that we're depending on a library that I wish had more community backing like the original serde_yaml did.

The alternative here would probably be foregoing YAML entirely and using TOML instead, but it seems the rest of the Robotmk ecosystem uses YAML, so it is probably best to remain consistent here.

Agreed. Given the constraint to use YAML, this seems fine to me.

@relrod
relrod merged commit 9fbe02d into Checkmk:main Oct 29, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants