complex capture filters

[alexminder]

What happened:

How to use complex capture selects based on multiple conditions?
It would be great to see documetation with good portion of such examples.

What you expected to happen:

Currently I don't know how to do such selects in a NNCP.

$ oc get nns NODE -o json|jq  '.status.currentState.interfaces|.[]|select(.driver == "igb" or .driver == "tg3")|.name'
"eno8303"
"eno8403"

This select does no allow to use integer in NNCP capture, because expected string, but nns returns float64:

$ oc get nns NODE -o json|jq  '.status.currentState.interfaces|.[]|select(.ethernet.speed == 10000)|.name'
"eno12399np0"
"eno12409np1"

[qinqon]

@alexminder is this issue for the k-nmstate "capture" feature or to compose a proper jq expression ?

[alexminder]

@qinqon the issue for k-nmstate "capture" feature.
jq as an example to illustrate the impossibility of using such expressions in "capture."

[qinqon]

@alexminder can you open an issue at github.com/nmstate/nmstate, we have move the captures "engine" there and we will integrate k-nmstate to what is there.

[qinqon]

@alexminder we are integrating nmstate policy engine into kubernetes-nmstate instead of the first golang implementation, this one supports strings, numbers and booleans for matching.

About multi match of field value we are thinking on implementing something like interfaces.driver == ( "igb" | "tg3" )

[alexminder]

@qinqon , Great! It should be enough.

[qinqon]

@alexminder so this one will allow strings, numbers and bools -> #1277

A follow up at nmstate will add complex matching expressions.