Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change CLI naming convention and update documentation #39

Merged
merged 5 commits into from
May 23, 2022

Conversation

tatry
Copy link
Collaborator

@tatry tatry commented May 16, 2022

No description provided.

@tatry tatry added this to In progress in C API & command line tool to manage PSA-eBPF programs via automation May 16, 2022
@tatry tatry linked an issue May 16, 2022 that may be closed by this pull request
@tatry tatry force-pushed the tatry/documentation branch 3 times, most recently from 0ee001e to 1236c47 Compare May 20, 2022 09:21
```shell
psabpf-ctl digest get pipe ID DIGEST

DIGEST := { id DIGEST_ID | name FILE | DIGEST_FILE }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be good to explain what is DIGEST_ID and DIGEST_FILE. This comment applies to all other commands too.

Also, it would be useful to explain what is the name format as a P4 developer may try to use extern name defined as defined in a P4 language while we require <Pipeline>_<extern name>, right? As this applies to all externs/objects, we can add such a note at the beginning of this document.

@tatry
Copy link
Collaborator Author

tatry commented May 23, 2022

PTF tests available in tatry/p4c#7

@osinstom osinstom changed the title Improve documentation Change CLI naming convention and update documentation May 23, 2022
@osinstom osinstom merged commit 706f34c into master May 23, 2022
C API & command line tool to manage PSA-eBPF programs automation moved this from In progress to Done May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Prepare docs with commands reference
2 participants