A dagger sdk written in rust for rust
Go to file
Kasper Juul Hermansen 4ce58a418c
add ci (#7)
* add ci

* with description

* fix warnings

* with actual test

* leave out tests for now as they rely on dind
2023-02-18 00:34:04 +00:00
.github/workflows add ci (#7) 2023-02-18 00:34:04 +00:00
ci add ci (#7) 2023-02-18 00:34:04 +00:00
crates fix(deps): update all dependencies (#5) 2023-02-17 23:00:42 +01:00
src feature/add impl (#6) 2023-02-17 12:33:16 +01:00
.gitignore Add base sdk 2023-01-27 08:31:09 +01:00
Cargo.lock add ci (#7) 2023-02-18 00:34:04 +00:00
Cargo.toml add ci 2023-02-17 23:10:52 +01:00
CHANGELOG.md v0.2.6 2023-02-17 23:06:26 +01:00
LICENSE.MIT set readme and license 2023-01-27 08:38:39 +01:00
README.md document usage 2023-02-17 18:00:20 +01:00
renovate.json Add renovate.json 2023-01-27 22:42:47 +00:00

dagger-rs

A dagger sdk written in rust for rust.

Usage

See dagger-sdk

Status

  • dagger cli downloader
  • dagger network session
  • graphql rust codegen (User API)
    • Scalars
    • Enums
    • Input
    • Objects
  • Implement context and querier
    • Marshaller
    • Querier
    • Context
    • Deserializer for nested response (bind)
  • Add codegen to hook into querier
  • fix build / release cycle
  • general api stabilisation
  • document usage
  • make async variant

Architecture

  • . Root project mainly used for generating the CLI, which in turn is used to bootstrap the code generation from dagger
  • crates/dagger-core Contains all base types used during actual usage. This is where the primary logic lives in which the user interacts (*disclaimer: most stuff haven't moved in here yet.)
  • crates/dagger-sdk Contains the actual sdk in which the user interacts, dagger-core is reexported through this API as well.
  • crates/dagger-codegen This is the bulk of the work, it takes the input graphql and spits out the API in which the user interacts, this is heavily inspired by other dagger-sdk's. It primarily turns graphql into rust code.