We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
capture.<key>
It may be more user-friendly and less error prone to refer to captured state via capture identity, instead of having to use a pipe.
capture
pipe
Consider the following nmpolicy snippet:
spec: capture: ethernets: interfaces.type=="ethernet" ethernets-up: capture.ethernets | interfaces.state=="up"
It would be nice if the pipe wasn't required to access a captured state, and allow referring to it directly by a path, like so:
spec: capture: ethernets: interfaces.type=="ethernet" ethernets-up: capture.ethernets.interfaces.state=="up"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It may be more user-friendly and less error prone to refer to captured state via
capture
identity, instead of having to use apipe
.Consider the following nmpolicy snippet:
It would be nice if the pipe wasn't required to access a captured state, and allow referring to it directly by a path, like so:
The text was updated successfully, but these errors were encountered: