What were you trying to do that didn't work?

The "capture" field has no way to speciy the order since it's a dictionary, if one of the capture entries references another not yet consumed nmstatectl fails

What is the impact of this issue to you?

When integration kubernetes-nmstate with nmstatectl policy this error pops up since the order of capture field is not relevant and it's marsharled without keeping the created order.

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Use the following policy at nmstatectl policy

capture:
  ethernets: interfaces.type=="ethernet"
  ethernets-lldp: capture.ethernets-up | interfaces.lldp.enabled:=true

  ethernets-up: capture.ethernets | interfaces.state=="up"
  ethernets-lldp-skip-eth-conf: >-
    capture.ethernets-lldp | interfaces.ethernet := null
desiredState:
  interfaces: '{{ capture.ethernets-lldp-skip-eth-conf.interfaces }}'

Steps to reproduce

Expected results

All the captures get resolved

Actual results

2.35 [2024-09-11T14:16:36Z WARN nmstate::iface] Unsupported interface type unknown NmstateError: PolicyError: Failed to find capture ethernets-lldp | {{ capture.ethernets-lldp.interfaces }} | ...........^