cwp edge pull
shipped 2.0.0cwp edge pull [env] [flags]
Acts on the local site. Name an environment to act there instead.
| Argument | What it is | Default |
|---|---|---|
[env] | environment to read (default: default_environment in cwp.yml) |
| Flag | What it does | Default |
|---|---|---|
--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 pull reads the settings of the zone in front of an environment and
writes them to edge/<env>.yml. So what a project runs at the edge is a file
in the tree like every other artifact. It writes only the settings the zone
answers. cwp leaves out a setting the zone does not report rather than
inventing one. A pull that changes nothing writes nothing.
# edge/live.yml
provider: cloudflare
zone: example.com
settings:
tls: full
script_rewriting: "off"
email_obfuscation: "on"
It writes nothing to the site, so it runs under --dry-run.
What it does not do
- It does not carry DNS.
- It does not write to the zone. That is
cwp edge push.