cwp edge push

cwp edge push [env] [flags]

Acts on the local site. Name an environment to act there instead.

tree → site

Argument	What it is	Default
[env]	environment to write (default: default_environment in cwp.yml)

Flag	What it does	Default
--force	override the protected-environment refusal	off
--no-backup	skip the remote backup taken before the write	on
--yes	skip the confirmation prompt	off
--with-agent	with —dry-run on a host with no shell: install and remove the PHP agent so the plan is real	off

Plus the shared flags --json, -v, --verbose, -q, --quiet and --dry-run.

What it does

edge push writes edge/<env>.yml to the zone and sets only what differs from what the zone holds. It is an upward write against a remote. So it takes the guards every upward write takes: the protected-environment refusal (--force), a remote backup first (--no-backup), and a confirmation that names each setting that changes.

$ cwp edge push live
✓ remote backup — …
? Set 1 edge setting(s) on live?
    tls: tree strict, zone full
✓ edge push (live) — tls: full → strict

After the write it reads the zone back and holds that every setting landed. It leaves a setting the tree omits as it is. The token must carry Zone Settings:Edit.

What it does not do

• It does not send a setting the file leaves out. An absent key is unmanaged, not “set to nothing”.
• It does not manage DNS or the perimeter. Those are their own commands.