tvl-depot/ops/yandex-cloud-rs
Vincent Ambo fd92ea9be3 fix(ops/yandex-cloud-rs): set license in Cargo manifest
Change-Id: Icc15953557585cbb2708a1267ab509caca8b258e
Reviewed-on: https://cl.tvl.fyi/c/depot/+/8600
Reviewed-by: tazjin <tazjin@tvl.su>
Autosubmit: tazjin <tazjin@tvl.su>
Tested-by: BuildkiteCI
2023-05-19 09:29:44 +00:00
..
examples feat(ops/yandex-cloud-rs): generated gRPC clients for Yandex Cloud 2023-04-28 12:50:33 +00:00
src feat(ops/yandex-cloud-rs): generated gRPC clients for Yandex Cloud 2023-04-28 12:50:33 +00:00
.gitignore feat(ops/yandex-cloud-rs): generated gRPC clients for Yandex Cloud 2023-04-28 12:50:33 +00:00
build.rs feat(ops/yandex-cloud-rs): generated gRPC clients for Yandex Cloud 2023-04-28 12:50:33 +00:00
Cargo.lock chore(ops/yandex-cloud-rs): bump API definitions (2023-05-19) 2023-05-19 09:23:08 +00:00
Cargo.toml fix(ops/yandex-cloud-rs): set license in Cargo manifest 2023-05-19 09:29:44 +00:00
default.nix chore(ops/yandex-cloud-rs): bump API definitions (2023-05-19) 2023-05-19 09:23:08 +00:00
README.md docs(ops/yandex-cloud-rs): add developer-facing README 2023-05-19 09:23:08 +00:00

yandex-cloud-rs

Client library for Yandex Cloud gRPC APIs, as published in their GitHub repository.

Please see the online documentation for user-facing information, this README is intended for library developers.

The source code of the library lives in the TVL repository.


In order to build this library, the gRPC API definitions need to be fetched from GitHub. By default this is done by Nix (see default.nix), which then injects the location of the API definitions through the YANDEX_CLOUD_PROTOS environment variable.

The actual code generation happens through the calls in build.rs.

Releases of this library are done from dirty trees, meaning that the version on crates.io should already contain all the generated code. In order to do this, after bumping the version in Cargo.toml and the API commit in default.nix, the following release procedure should be used:

# Get rid of all generated source files
cd src
ls | grep -v '^lib.rs$' | xargs rm
cd ..

# Get rid of all old artefacts
cargo clean

# Verify that a clean build works as intended
cargo build

# Verify that all documentation builds, and verify that it looks fine:
#
# - Is the version correct (current date)?
# - Are all the services included (i.e. not an accidental empty build)?
cargo doc --open

# If everything looks fine, release:
cargo publish --allow-dirty