Developing an extension outside the eBPF repo has unclear steps #3021
Labels
bug
Something isn't working
documentation
Improvements or additions to documentation
P2
triaged
Discussed in a triage meeting
Milestone
Describe the bug
The documentation in epfExtensions.md does not describe how the following fields should be defined when creating a new hook point:
It is not clear whether these should be defined in the eBPF repo or only in the codebase of the new extension. It is also not clear how the
bpf_link_type
enum should be used.At a higher level, the sample code referenced in the documentation should ideally provide an example that would work outside of the eBPF repo. Finally, ideally the steps to build the sample code would rely only on the nuget package produced by the build, and the sample would be built and tested in automation, providing confidence that the sample is a good reference point for third party developers.
OS information
N/A.
Steps taken to reproduce bug
Expected behavior
The docs should provide clear guidance for various scenarios, and the sample code should be able to be copied into a standalone codebase and work with minimal changes.
Actual outcome
The docs and sample code led to confusion and some mild frustration.
Additional details
No response
The text was updated successfully, but these errors were encountered: