16 unstable releases (7 breaking)

0.8.0 Jan 24, 2024
0.7.0 Oct 18, 2023
0.6.0 May 30, 2023
0.5.0 Mar 19, 2023
0.1.6 Mar 5, 2021

#1182 in Network programming

Download history 120/week @ 2023-12-04 177/week @ 2023-12-11 83/week @ 2023-12-18 15/week @ 2024-01-01 40/week @ 2024-01-08 85/week @ 2024-01-15 133/week @ 2024-01-22 62/week @ 2024-01-29 3/week @ 2024-02-05 52/week @ 2024-02-12 49/week @ 2024-02-19 80/week @ 2024-02-26 21/week @ 2024-03-04 42/week @ 2024-03-11 75/week @ 2024-03-18

219 downloads per month
Used in 2 crates

MIT license

6MB
135K SLoC

C 105K SLoC // 0.2% comments Rust 28K SLoC // 0.0% comments Forge Config 836 SLoC // 0.7% comments Shell 418 SLoC // 0.2% comments TCL 321 SLoC // 0.3% comments RPM Specfile 98 SLoC Bitbake 4 SLoC

yang2-rs

Crates.io Documentation MIT licensed Build Status codecov

Rust bindings for the libyang2 library.

For raw FFI bindings for libyang2, see libyang2-sys.

Cargo.toml

[dependencies]
yang2 = "0.9"

Design Goals

  • Provide high-level bindings for libyang2 using idiomatic Rust
  • Leverage Rust's ownership system to detect API misuse problems at compile time
  • Automatic resource management
  • Zero-cost abstractions

Feature flags

By default, yang2-rs uses pre-generated FFI bindings and uses dynamic linking to load libyang2. The following feature flags, however, can be used to change that behavior:

  • bundled: instructs cargo to download and build libyang2 from the sources. The resulting objects are grouped into a static archive linked to this crate. This feature can be used when having a libyang2 dynamic link dependency isn't desirable.
    • Additional build requirements: cc 1.0, cmake 0.1, a C compiler and CMake.
  • use_bindgen: generate new C FFI bindings dynamically instead of using the pre-generated ones. Useful when updating this crate to use newer libyang2 versions.
    • Additional build requirements: bindgen 0.55.0

Example

A basic example that parses and validates JSON instance data, and then converts it to the XML format:

use std::sync::Arc;
use std::fs::File;
use yang2::context::{Context, ContextFlags};
use yang2::data::{
    Data, DataFormat, DataParserFlags, DataPrinterFlags, DataTree,
    DataValidationFlags,
};

static SEARCH_DIR: &str = "./assets/yang/";

fn main() -> std::io::Result<()> {
    // Initialize context.
    let mut ctx = Context::new(ContextFlags::NO_YANGLIBRARY)
        .expect("Failed to create context");
    ctx.set_searchdir(SEARCH_DIR)
        .expect("Failed to set YANG search directory");

    // Load YANG modules.
    for module_name in &["ietf-interfaces", "iana-if-type"] {
        ctx.load_module(module_name, None, &[])
            .expect("Failed to load module");
    }
    let ctx = Arc::new(ctx);

    // Parse and validate data tree in the JSON format.
    let dtree = DataTree::parse_file(
        &ctx,
        File::open("./assets/data/interfaces.json")?,
        DataFormat::JSON,
        DataParserFlags::empty(),
        DataValidationFlags::NO_STATE,
    )
    .expect("Failed to parse data tree");

    // Print data tree in the XML format.
    dtree
        .print_file(
            std::io::stdout(),
            DataFormat::XML,
            DataPrinterFlags::WD_ALL | DataPrinterFlags::WITH_SIBLINGS,
        )
        .expect("Failed to print data tree");

    Ok(())
}

Note the NO_STATE flag passed to parse_file since the example json file does not contain state data. More examples can be found here.

License

This project is licensed under the MIT license.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/rwestphal/yang2-rs.

No runtime deps