Copying one object

Sometimes you don’t want a venue. You want one WLAN — with its portal, its RADIUS profile, its DPSK pool, and everything else it quietly depends on — moved into another tenant.

That is element copy. It ships with the Copy feature, alongside venue copy, and reuses the same MOP engine, the same review-and-arm cycle, and the same undo.

What you can start from

Three element types:

type	The object
wlan	A WLAN (Wi-Fi network)
switchProfile	A switch profile, with its VLANs and ACLs
ethernetPortProfile	An AP ethernet-port (LAN-port) profile

The point is the closure, not the object. Extracting a WLAN pulls in the shared objects it binds — portal service profile, RADIUS server profiles, DPSK pool and its identity group, VLAN pool, Wi-Fi calling profile, access-control profile and its four child policies — because a WLAN recreated without them is not a working WLAN.

Call element_copy_support for the authoritative list of which domains an element copy carries. It is a filtered view of the venue-copy matrix: the tenant-scoped shared objects reachable downstream of an element, and nothing venue-scoped.

The pipeline

1. element_extract — identify the object by type plus either id (preferred, unambiguous) or name (matched exactly, and refused if more than one object shares it). Optionally connection to read from a non-default tenant. Like venue_extract it is chunked: if it comes back complete: false, call it again with the same snapshotId.

2. element_copy_plan — pass the completed snapshotId and targetConnection. It compiles an apply-MOP that creates the element and its whole closure in the target tenant and wires them to each other. It writes nothing.

3. mop_replay { mopId, dryRun: true } — review every step.

4. mop_replay { mopId, armWrites: true } — run it. Arming names the target tenant first.

5. element_copy_verify — confirm it landed.

Reverse it with venue_copy_undo { runId }. No venue is deleted, because none was created.

Two things that surprise people

It must be cross-tenant

Caution

A same-tenant element copy writes nothing and produces no MOP. The copy names every object exactly as the source does, so each one collides with itself and R1 refuses the duplicate name.

If you want the object on another venue in the same tenant, that is a venue copy, not an element copy. Element copy is for moving an object to a different tenant.

Nothing is activated

An element copy has no venue to activate on, so the element and its closure are created and fully wired — and then left unactivated. Activate them where you want them live afterwards.

This is the deliberate difference from a venue copy, which activates as it goes. It also means element copy carries no venue-scoped configuration at all: no AP radio, mesh, LED, or syslog settings, no AAA servers, no AP groups. Those belong to a venue.

Name collisions in the target

The second copy into a tenant you have copied into before is the normal case, and sharedCollision governs it — the same setting, the same three values, and the same default (adopt) as a venue copy. Matching is by name only; contents are never compared.

Element copy also takes a collisionPolicy of skip (default) or overwrite for the element itself.

Note

adoptExisting still works and is superseded by sharedCollision, where adoptExisting: false means sharedCollision: "skip". Prefer sharedCollision — it is the only one that offers overwrite.

Verifying

element_copy_verify queries the target tenant for the exact name of every object the copy actually creates, and reports present or missing. Its checklist comes from the same plan the copy compiled, so pass the same sharedCollision and domains the copy used — a different policy checks a different list than the copy created.

It separates three outcomes:

• Checked — objects the copy creates, name-verified in the target.
• adoptedObjects — objects that already existed and were adopted. These are never name-checked, because the name that would prove them present belongs to the pre-existing object.
• plannedSkips — objects the compiler deliberately dropped.

Note

This is a name-existence check, not a field-level re-diff. An element copy has no target venue to re-extract, so it cannot reach venue_copy_verify’s depth — and it says so in its own response.

Next steps

Venue config copy The whole-venue pipeline, and the collision policies element copy shares.

What a venue copy carries The full per-domain matrix that element_copy_support filters.

Venue backups Keeping a whole venue's configuration rather than moving one object.

Multiple connections Saving the target tenant an element copy writes to.