akamai_ccu 1.4.0 → 1.4.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +3 -3
- data/lib/akamai_ccu/cli.rb +1 -1
- data/lib/akamai_ccu/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 54fe3c8b980c14e50ef78c4789eab9e376609733
|
|
4
|
+
data.tar.gz: c1603bc6a64a685d5ba73eed5c968b3d02888373
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 0b04c3c310a4db4c85e17dd638b78be47774b05caec0b4aeb4a3778a6df054aa387a97555b460d97ac128ddc97cc746a89158b766179ccfe24c6f6b2b0f2b103
|
|
7
|
+
data.tar.gz: e1517ac58e83c73cc563a7407da7e0e38824f58343ce370d2cf095a37638bbdec39fde099271de7c604cf2052a7a9affe2209d0c4cf2c08102138a7f44a96111
|
data/README.md
CHANGED
|
@@ -65,7 +65,7 @@ gem install akamai_ccu
|
|
|
65
65
|
This gem requires you have a valid Akamai Luna Control Center account, enabled to add APIs clients.
|
|
66
66
|
Upon APIs client creation, you'll get the `client token` to be used to generate new APIs credentials data: these consist of a secret key, two token (client and access) and a dedicated host for API authorization.
|
|
67
67
|
Check Akamai's [official documentation](https://developer.akamai.com/introduction/Conf_Client.html) for more details.
|
|
68
|
-
|
|
68
|
+
You have two main options to import credentials data:
|
|
69
69
|
|
|
70
70
|
#### edgerc
|
|
71
71
|
You can generate (using a script or by hand) an INI file named `.edgerc`:
|
|
@@ -117,7 +117,7 @@ AkamaiCCU::Wrapper.setup(secret)
|
|
|
117
117
|
|
|
118
118
|
#### Edge network
|
|
119
119
|
Purging actions runs on the `staging` network by default.
|
|
120
|
-
Switch to production by just appending a shebang `!` on the method name.
|
|
120
|
+
Switch to `production` network by just appending a shebang `!` on the method name.
|
|
121
121
|
|
|
122
122
|
#### Invalidating
|
|
123
123
|
The CCU V3 APIs allow for invalidating contents by URLs or content provider (CP) codes: currently only the former relies on the Fast Purge Utility.
|
|
@@ -154,7 +154,7 @@ You can use the CLI by:
|
|
|
154
154
|
Calling the help for the specific action:
|
|
155
155
|
```shell
|
|
156
156
|
ccu_invalidate -h
|
|
157
|
-
Usage:
|
|
157
|
+
Usage: ccu_invalidate --edgerc=./.edgerc --production --cp="12345, 98765"
|
|
158
158
|
-e, --edgerc=EDGERC Load secret by .edgerc file
|
|
159
159
|
-t, --txt=TXT Load secret by TXT file
|
|
160
160
|
-c, --cp=CP Specify contents by provider (CP) codes
|
data/lib/akamai_ccu/cli.rb
CHANGED
|
@@ -54,7 +54,7 @@ module AkamaiCCU
|
|
|
54
54
|
|
|
55
55
|
private def parser
|
|
56
56
|
OptionParser.new do |opts|
|
|
57
|
-
opts.banner = %Q{Usage: #{@action} --edgerc=./.edgerc --production --cp="12345, 98765"}
|
|
57
|
+
opts.banner = %Q{Usage: ccu_#{@action} --edgerc=./.edgerc --production --cp="12345, 98765"}
|
|
58
58
|
|
|
59
59
|
opts.on("-eEDGERC", "--edgerc=EDGERC", "Load secret by .edgerc file") do |secret|
|
|
60
60
|
@secret = File.expand_path(secret)
|
data/lib/akamai_ccu/version.rb
CHANGED