Is external usage of the api_client "supported"? #7671
Replies: 2 comments
-
|
The current philosophy is that use of crates inside the CH project by code outside the project are "at your own risk". APIs will change without version bumps. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ok, that sounds fair. Thanks for the guidance |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi folks, In kata-containers we are using (a very old version of) the api_client crate as part of our cloud-hypervisor work in our new(ish) rust based runtime (see https://github.com/kata-containers/kata-containers/blob/e430b2641c452f168148c8d18c5d33e42ff991f2/src/runtime-rs/crates/hypervisor/ch-config/Cargo.toml#L20-L24 for the exact usage).
The usage seems pretty small and limited to:
as far as I can tell.
This work was done by members of the community who left the project a long time ago and someone raised a suggestion today that this approach was taken against the wishes of the cloud-hypervisor community as this crate is internal for you we should not be using it. Is this the case? Obviously we want to respect your community, so ensure that we don't "support", or try and update the api_client crate if we shouldn't be using it.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions