|
| 1 | +.TH CLI4 1 |
| 2 | + |
| 3 | +.SH NAME |
| 4 | +cli4 \- Command line access to CloudFlare v4 API |
| 5 | + |
| 6 | +.SH SYNOPSIS |
| 7 | +.B cli4 |
| 8 | +[\fB\-h\fR|\fB\-\-help] |
| 9 | +[\fB\-v\fR|\fB\-\-verbose] |
| 10 | +[\fB\-q\fR|\fB\-\-quiet] |
| 11 | +[\fB\-j\fR|\fB\-\-json] |
| 12 | +[\fB\-y\fR|\fB\-\-yaml] |
| 13 | +[\fBitem\fR=\fIvalue\fR ...] |
| 14 | +.IR /command ... |
| 15 | + |
| 16 | +.SH DESCRIPTION |
| 17 | +.B cli4 |
| 18 | +provides command line access to CloudFlare v4 API |
| 19 | + |
| 20 | +.SH OPTIONS |
| 21 | +.TP |
| 22 | +.IP "[\-h, \-\-help]" |
| 23 | +This information (in a terse form). |
| 24 | +.IP "[\-v, \-\-verbose]" |
| 25 | +Provide some protcol debugging information. |
| 26 | +.IP "[\-q, \-\-quiet]" |
| 27 | +Don't output any JSON/YAML responses |
| 28 | +.IP "[\-j, \-\-json]" |
| 29 | +Output in JSON format |
| 30 | +.IP "[\-y, \-\-yaml]" |
| 31 | +Output in YAML format |
| 32 | +.IP \-\-get |
| 33 | +Send HTTP request as a \fBGET\fR (the default). |
| 34 | +.IP \-\-patch |
| 35 | +Send HTTP request as a \fBPATCH\fR. |
| 36 | +.IP \-\-post |
| 37 | +Send HTTP request as a \fBPOST\fR. |
| 38 | +.IP \-\-put |
| 39 | +Send HTTP request as a \fBPUT\fR. |
| 40 | +.IP \-\-delete |
| 41 | +Send HTTP request as a \fBDELETE\fR. |
| 42 | +.IP item=\fIvalue\fR |
| 43 | +Set a paramater or data value to send with a \fBGET\fR, \fBPATCH\fR, \fBPOST\fR, \fBPUT\fR or \fBDELETE\fR command. The value is sent as a string. |
| 44 | +.IP item:=\fIvalue\fR |
| 45 | +Set a paramater or data value to send with a \fBGET\fR, \fBPATCH\fR, \fBPOST\fR, \fBPUT\fR or \fBDELETE\fR command. The value is sent as an interger. |
| 46 | +.IP /command... |
| 47 | +The API command. |
| 48 | +The command uses slash (\fB/\fR) to seperate the verbs in the same way that the CloudFlare v4 API documentation does. |
| 49 | +Any verb starting with colon (\fB:\fR) is either converted to zone_id, user_id, organtization_id, or otherwise. |
| 50 | + |
| 51 | +.SH RESULTS |
| 52 | +The output is either JSON or YAML formatted. |
| 53 | + |
| 54 | +.SH EXAMPLES |
| 55 | +.B cli4 /zones |
| 56 | +List infomation for all zones. |
| 57 | +.B cli4 /zones/:example.com |
| 58 | +List specific zone info. |
| 59 | +.B cli4 /zones/:example.com/settings |
| 60 | +List settings for a specific zone. |
| 61 | +.B cli4 --delete purge_everything=true /zones/:example.com/purge_cache |
| 62 | +Purge cache for a specific zone. |
| 63 | +.B cli4 --delete files='[http://example.com/css/styles.css]' /zones/:example.com/purge_cache |
| 64 | +Purge cache for a specific zone. |
| 65 | +.B cli4 --delete files='[http://example.com/css/styles.css,http://example.com/js/script.js] /zones/:example.com/purge_cache |
| 66 | +Purge cache for a specific zone. |
| 67 | +.B cli4 --delete tags='[tag1,tag2,tag3]' /zones/:example.com/purge_cache |
| 68 | +Purge cache for a specific zone. |
| 69 | +.B cli4 /zones/:example.com/available_plans |
| 70 | +List available plans for a zone. |
| 71 | +.B cli4 --patch status=active /zones/:example.com/dnssec |
| 72 | +Make DNSSEC active for specfic zone. |
| 73 | +.B cli4 /zones/:example.com/dnssec |
| 74 | +List DNSSEC infomation and status for a specific zone. |
| 75 | + |
| 76 | +.SH SEE ALSO |
| 77 | +The CloudFlare API can be found https://api.cloudflare.com/. Each API call is provided via a similarly named function within the CloudFlare class. |
0 commit comments