Check for drift

Drift is NetBox changing under a deployment: someone edits a field the design sets, or deletes an object it created. Planning the deployment again shows it. The tutorial's Check for drift makes some and finds it.

1. Go to Deployments and open the deployment.
2. Select Check drift. It plans the deployment again in the background, with the design and variables it was applied with, and stays on the page.

In sync means NetBox still matches the design. Drifted says how many changes the plan found: Review opens it, showing each field NetBox changed and the value the design sets, and each object the deployment created that NetBox no longer has. Apply the plan to put them back.

A deployment of several designs has Check drift of all above its designs. It checks each from the plan that applied it, reading NetBox once, and sums them up: in sync when every design is, or how many objects differ and in how many designs, with an object two designs share counted once. Each design's own result and Review stay in its section, because a plan is per design and there is no one plan to apply.

Only what the design declares counts. A field the design doesn't set can be changed in NetBox freely: it is never reported as drift, and applying never touches it.

Check drift compares NetBox with the version of the design the deployment applied, so a design edited since is not reported as drift; the Deployments page says the design has changed instead, and Redeploy is how you move to it.

Sessions

Each round of planning is a session, listed under its deployment.

• Replan plans an open session again, with the same variables. Only a session's newest plan can be applied.
• Discard plan closes an open session you don't need, and its plan can't be applied. Nothing in NetBox changes.

An applied session has no actions of its own. To plan its deployment again, or change its variables, use Redeploy on the deployment: it starts a new session from the variables the deployment was applied with.