apidragon 1.6.2 → 1.6.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 0d574a6823e741959e5a118293c024bda6976c10
4
- data.tar.gz: 1f2837d48a7f9efde33b6f54fe7a6701df30ff92
3
+ metadata.gz: e31b95bb29649a3b9e722d350f3f1d379c1a92c3
4
+ data.tar.gz: 7e58913b63fa44a2fd50c0227fed1db96341be1a
5
5
  SHA512:
6
- metadata.gz: bdf123732451aa9f62564945a9140f43824c04162da3a0369e5d14c62e9ed9daa94584e83bcefa577648904738fe425af990295fc0bb8dc0a10eb0885559485b
7
- data.tar.gz: c5ab8987a6a25209d03f4065f7d463ec8f233d9e0821bc9ad07c079056baa69b8e2f45d472caa73dc359067f461b2678507b604f243e1dc7721f6f460cde506c
6
+ metadata.gz: ebb00c0e7384bf6a56ce76dd7c9dabd1e8d8ebcacf86545214424cc6071f94f48559736a0a20558cf6c72b67a259cb860870cd0a0bcc22b0aadd629ebf5b7b75
7
+ data.tar.gz: d4cc03881880e41474ba5dfd59532773c351721680adebec5123a986ecaabb67f58d408a4106d2f29a2018d62a4e9669302ed9ea9e4329e4e208db6ed5d8aa1d
data/README.md CHANGED
@@ -12,7 +12,7 @@ These classes run a sequence of API calls using a configuration file.
12
12
  # How to Use:
13
13
 
14
14
  - `gem install apidragon`
15
- - Create `/tmp/apidragonconf.yaml` according to the examples below
15
+ - Create `apidragonconf.yaml` according to the examples below
16
16
  - Run from the command line with `apidragon do [command]`
17
17
  `[command]` is the name of one of the `macros` defined in the config file. So if I was using the config in the example,
18
18
  I could run `apidragon do macro_1`, which would then call `testcall` and `testcall2` in the order specified.
@@ -20,7 +20,7 @@ I could run `apidragon do macro_1`, which would then call `testcall` and `testca
20
20
  - You can specify you password or username from the command line with `apidragon do [command] --username [username] --password [password]` (recommended if you don't want to store credentials in a file)
21
21
 
22
22
  # Configuration:
23
- Create `/tmp/apidragonconf.yaml`. It can contain any variables you need to access the API you are using, as well as `macros`.
23
+ Create `apidragonconf.yaml`. It can contain any variables you need to access the API you are using, as well as `macros`.
24
24
  - Example config:
25
25
  ```yaml
26
26
  ---
@@ -147,6 +147,7 @@ Loggin can be disabled by specifying `logging` to be `false`, as per below.
147
147
  ```
148
148
 
149
149
  ## plugin
150
+ Note: The default folder for plugins is `/usr/local/apidragonplugins`. Create this folder and writing any plugin files to it usually requires root permissions.
150
151
  Each call can refer to a plugin file. The Plugin class should follow the structure outlined below.
151
152
  - e.g.:
152
153
  - example.rb (@ /tmp/apidragonplugins/)
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.6.2
1
+ 1.6.3
data/bin/apidragon CHANGED
@@ -6,7 +6,7 @@ require_relative '../lib/apidragon.rb'
6
6
 
7
7
  Commander.configure do
8
8
  program :name, 'apidragon'
9
- program :version, '1.6.2'
9
+ program :version, '1.6.3'
10
10
  program :description, 'CLI for automating api requests'
11
11
  program :help, 'Author', 'Isaiah Thiessen <isaiah.thiessen@telus.com>'
12
12
 
data/lib/apidragon/api.rb CHANGED
@@ -6,7 +6,7 @@ require_relative 'macro'
6
6
  require_relative 'argbucket'
7
7
 
8
8
  DEFAULT_CONFIG = '/tmp/apidragonconf.yaml'
9
- PLUGINS = '/tmp/apidragonplugins/'
9
+ PLUGINS = '/usr/local/apidragonplugins/'
10
10
  LOG = '/tmp/apidragon.log'
11
11
 
12
12
  class Api < ArgBucket
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: apidragon
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.6.2
4
+ version: 1.6.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - isaiah thiessen