In the initial iteration, it was fetching flow from v2/flows/, which works and it facilitates to also get the instructions converted, but it has the drawback that depending on consistency check or network delays it can result in false positive. v2/stored_flows/ store all managed flows and that's the source of the truth that telemetry_int should rely on. Also, it should also filter for state="pending" or "state=installed", "pending" is just a transitory state, but it can happen.
actions should be converted to instructions since historically on flow_manager we've been still accepting OF1.0 actions payload format.
In the initial iteration, it was fetching flow from
v2/flows/, which works and it facilitates to also get theinstructionsconverted, but it has the drawback that depending on consistency check or network delays it can result in false positive.v2/stored_flows/store all managed flows and that's the source of the truth thattelemetry_intshould rely on. Also, it should also filter forstate="pending"or"state=installed","pending"is just a transitory state, but it can happen.actionsshould be converted toinstructionssince historically onflow_managerwe've been still accepting OF1.0 actions payload format.