Pull from EVE¶

Pull from EVE is reconcile with direction from_eve. It updates Git files from the managed lab. It is not Import.

	Import	from_eve
When	First adoption of a source lab	Refresh an existing IaC project
Input	source_lab	project + managed_lab
Effect	New Git project + managed clone	Local file/state updates
Must not	Mutate source_lab	Clone source, relabel as Import, replace/destroy the managed lab

Omitted direction is to_eve. The UI copy is Reconcile / Pull from EVE. Do not think in terms of push/pull as request values.

from_eve does not send EVE POST/PUT/DELETE. Confirm does not authorize stop. A vanished live object becomes an explicit delete-local, not topology prune. prune is a to_eve delete of extra live objects.

After a pull, review the Git diff and commit it yourself. Presentation YAML is not replayed on ordinary reconcile.

Running configuration¶

from_eve reads the persisted EVE lab, including startup-config blobs already stored on that lab. It does not read NOS memory.

Export running config (node menu, canvas selection, or MCP eve_iac_export_config) copies the running configuration into an existing set first. configset is required: default, or a set already on the lab. An unknown name is not created. The export does not write topology.yml or configs/**. Confirm is required, including when Live config apply is on. Then Pull from EVE if that blob should become Git intent.

See directions and plan / reconcile.