cipherpipe 0.3.0 → 0.4.0

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
  SHA256:
3
- metadata.gz: 9fbd9abc8551bd0d9d03d7fd91e1d4eb1c57ca0bffd8d12c0d8a13412fc23e8e
4
- data.tar.gz: cbfee38900e2ed2bd30328c1789532fa53f3aa6f27b8ea56c0296948e97a9439
3
+ metadata.gz: 6e12aef1cfb6098aaf1d7ddece3e605b5655d754f125539bb94cc5cb3347866a
4
+ data.tar.gz: 1fb2bcf130d88fc08b33e47025c61caec9f0d23fae4b8e013785e75650513540
5
5
  SHA512:
6
- metadata.gz: 3ae3d44347e9f054c72bc838e83ff29d50e848dc46f47ab4aa78dbf0c114749141184037488452b48c986e13cc48a82fb93df594dbeaa4836632df366644bc35
7
- data.tar.gz: '0079cb88864cd97ffea062d65ffdbd96ce20d3a4ab3b7fc0c5c44be67bc135102926d6ac939ebf39f13129654729f893466363f8a1555430fff7afad35b82257'
6
+ metadata.gz: dc393bc0e8ddbf33cc541a8e130678f21b9c8ce8f59bb3eee990777d6e406a4dcdebd4a31e550fce0d06bc3ab8ac3c0c186b8211c935e23b0287e06abf4a9d6f
7
+ data.tar.gz: c5f2dee8cd41888d9cba04207f47f920c5949f007f7024f105bacf264083ae36ae3054bb7b7fcbe5b484062d14531863e69c3a4210308c7fe60a799f7eec7f9c
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- cipherpipe (0.3.0)
4
+ cipherpipe (0.4.0)
5
5
 
6
6
  GEM
7
7
  remote: https://rubygems.org/
data/README.md CHANGED
@@ -42,7 +42,7 @@ Everything for Cipherpipe is managed in a YAML configuration file `.cipherpipe.y
42
42
 
43
43
  When setting a Vault source, the destination is a key-value store (v2) and the `secret/` prefix is added automatically. When setting up 1Password, the destination is the name of the document, and you'll want to specify a vault as well.
44
44
 
45
- Here's an example for a Rails application using `dotenv` (and `ENVIRONMENT` is automatically translated to the appropriate Rails environment, as based on the RAILS_ENV variable):
45
+ Here's an example for a Rails application using `dotenv` (and `ENVIRONMENT` is automatically translated to the appropriate Rails environment, as based on the CIPHERPIPE_ENV or RAILS_ENV variables):
46
46
 
47
47
  ```yml
48
48
  file: .env.ENVIRONMENT
@@ -1,6 +1,6 @@
1
1
  Gem::Specification.new do |spec|
2
2
  spec.name = "cipherpipe"
3
- spec.version = "0.3.0"
3
+ spec.version = "0.4.0"
4
4
  spec.authors = ["Pat Allan"]
5
5
  spec.email = ["pat@freelancing-gods.com"]
6
6
 
@@ -1,5 +1,8 @@
1
1
  class Cipherpipe::Commands::EC2
2
- TOKEN_FILE = File.expand_path("~/.vault-token")
2
+ TOKEN_FILE = ENV.fetch(
3
+ "CIPHERPIPE_TOKEN_FILE",
4
+ File.expand_path("~/.vault-token")
5
+ )
3
6
 
4
7
  def self.call(configuration = nil)
5
8
  new(configuration).call
@@ -8,7 +8,10 @@ class Cipherpipe::Vault::EC2Token
8
8
  "http://169.254.169.254/latest/dynamic/instance-identity/pkcs7"
9
9
  )
10
10
 
11
- NONCE_FILE = File.expand_path "~/.cipherpipe-nonce"
11
+ NONCE_FILE = ENV.fetch(
12
+ "CIPHERPIPE_NONCE_FILE",
13
+ File.expand_path("~/.cipherpipe-nonce")
14
+ )
12
15
 
13
16
  def self.call(external_source)
14
17
  new(external_source).call
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: cipherpipe
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.0
4
+ version: 0.4.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Pat Allan
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2018-06-14 00:00:00.000000000 Z
11
+ date: 2018-08-17 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler