Skip to content

ezgh waf update

Change a WAF.

Updated View as Markdown
ezgh waf update <waf> [--name n] [--description d] [--mode block|log] [--managed-rule-set name[=log]…] [--logging off|matched|all] [--from-file waf.json] [flags]

Change a WAF. Only what’s given changes; --tag replaces all its tags, --clear-tags removes them, and --managed-rule-set replaces the list of managed rule sets (a set it already runs keeps its paranoia level and rule overrides). A change applies to every load balancer it’s attached to.

--from-file replaces the whole WAF with a JSON document: edit what ezgh waf get -o json prints. If the WAF changed after that, nothing is changed.

Part of ezgh waf.

Examples

ezgh waf update waf_k2m9x0a7qpe4 --mode block
ezgh waf update waf_k2m9x0a7qpe4 --logging all --logging-environment prod
ezgh waf get waf_k2m9x0a7qpe4 -o json > waf.json && ezgh waf update waf_k2m9x0a7qpe4 --from-file waf.json

Flags

Flag Type Default Description
--clear-tags boolean remove its tags
--description string what it’s for
-f, --from-file string the WAF as JSON (what ezgh waf get -o json prints), - for stdin; flags change it further
--logging string request logs to Obs: off, matched (the requests a rule matched) or all
--logging-environment string the Obs environment in the project request logs go to
--managed-rule-set string, repeatable a managed rule set to run, name or name=log (ezgh/core, ezgh/php, ezgh/node, ezgh/known-bad-inputs); repeat for more, in order, replacing the list
--mode string block, or log to record what it would block and block nothing
--name string a new name
--tag string, repeatable a tag, key=value; repeat for more

This command also takes the global flags.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close