Merge pull request #3318 from jodh-intel/docs-agent-protoc

docs: Clarify where to run agent API generation commands
This commit is contained in:
Archana Shinde 2021-12-21 00:28:01 -08:00 committed by GitHub
commit ae271a7e7b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -63,11 +63,15 @@ The Kata runtime communicates with the Kata agent using a ttRPC based API protoc
This ttRPC API is defined by a set of [protocol buffers files](protocols/protos). This ttRPC API is defined by a set of [protocol buffers files](protocols/protos).
The protocol files are used to generate the bindings for the following components: The protocol files are used to generate the bindings for the following components:
| Component | Language | Generation method | Tooling required | | Component | Language | Generation method `[*]` | Tooling required |
|-|-|-|-| |-|-|-|-|
| runtime | Golang | Run, `make generate-protocols` | `protoc` | | runtime | Golang | Run, `make generate-protocols` | `protoc` |
| agent | Rust | Run, `make` | | | agent | Rust | Run, `make` | |
> **Key:**
>
> `[*]` - All commands must be run in the agent repository.
If you wish to change the API, these files must be regenerated. Although the If you wish to change the API, these files must be regenerated. Although the
rust code will be automatically generated by the rust code will be automatically generated by the
[build script](protocols/build.rs), [build script](protocols/build.rs),