I was using ziti fabric inspect data-model-index as a cluster convergence gate for ZET testing: after an MFA TOTP enrollment (add identity, enable MFA, verify MFA), wait until all three controllers report the same index before toggling the identity off/on and re-authenticating. The gate passes but the re-auth still intermittently lands on a controller that hasn't applied the MFA write, so the index was giving a thumbs up while 2/3 controllers weren't tracking it.
ziti fabric inspect data-model-index seems to be pulling the raft index as seen by the router data model, and should pull the actual raft index instead.
I was using
ziti fabric inspect data-model-indexas a cluster convergence gate for ZET testing: after an MFA TOTP enrollment (add identity, enable MFA, verify MFA), wait until all three controllers report the same index before toggling the identity off/on and re-authenticating. The gate passes but the re-auth still intermittently lands on a controller that hasn't applied the MFA write, so the index was giving a thumbs up while 2/3 controllers weren't tracking it.ziti fabric inspect data-model-indexseems to be pulling the raft index as seen by the router data model, and should pull the actual raft index instead.