Add allow / block list for global helper functions which can be overridden by extensions #1842
Replies: 5 comments
-
I'm not yet convinced we would not want extensions to overload map related helper functions... what if an extension wanted to add a new map type? It could do that with an override. Otherwise we'd need a way to let extensions add map types, which we don't have yet. |
Beta Was this translation helpful? Give feedback.
-
Map operations was just an example that I mentioned. Per our earlier discussion, there was a concern on what if ebpfcore does not want the extensions to override some specific global helper functions. Adding the allow / block list will let ebpfcore control which global helper functions can be overridden. |
Beta Was this translation helpful? Give feedback.
-
I agree it would. I just don't know of a reason to do it now, so we should hold off doing anything until we have a need. If we never have a need, then this issue could just be closed. Maybe this should be converted to a discussion and only converted back to an issue if/when there is a need? |
Beta Was this translation helpful? Give feedback.
-
Agree that there is no use case right now. We can also probably move this issue to backlog and revisit if/when needed? |
Beta Was this translation helpful? Give feedback.
-
Per discussion in the triage meeting, we can close this for now, and revisit if there is a need in future. |
Beta Was this translation helpful? Give feedback.
-
Add support for a
allow
orblock
list of global helper functions which can be overloaded by extension.For example, we would not want extensions to overload map related helper functions.
Beta Was this translation helpful? Give feedback.
All reactions