envkey 1.2.7 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e92c011838d0bb0b29442dd688be0af1790977b0
-  data.tar.gz: 6e541a1cf2df57a20e59ebd1c92e608bcc8df3b9
+  metadata.gz: 9a5018a501d4e9a5bf02258fdc732dea2bbeb405
+  data.tar.gz: 031547f50b2f416441d85501065d8d1dd548d363
 SHA512:
-  metadata.gz: e0a1f9d1f9204b7fb6a6288215d16a2a344f8d33806a7877c2395bb162d8f55636916d2642599d10345c064c6beefe8eb532ec374fe8521ed086bd02b22a3d66
-  data.tar.gz: b3cdb8935339bb535289cfa606a34e699a652fee5fe0eef1cfc181c4f07150f085ada63a8af3610de199936167a7d560c47a73c8db32ea03bbdd001200663213
+  metadata.gz: d1f2dfd2a4a1ffcd0bdf1309046a6317fd586c66427a4fabc4b9a4716f081629b7ba621487110e7490601e42a345dd4ffe15b22ea03c158cb0404e1fda895e80
+  data.tar.gz: 541038a63c0270ad2aadfc4f8c1e4180b14da72a1d41233ab703f49dc784e1740505831ea01f86d4f25f795d13a46ec84d2093620562b38b40f5bd9417374b83

data/README.md

@@ -63,6 +63,13 @@ For caching purposes, the gem assumes you're in development mode if either `ENV[
 
 If you look in the `ext` directory of this gem, you'll find a number of `envkey-fetch` binaries for various platforms and architectures. These are output by the [envkey-fetch Go library](https://github.com/envkey/envkey-fetch). It contains EnvKey's core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It is completely open source.
 
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when the envkey gem attempts to load your config. [envkey-fetch](https://github.com/envkey/envkey-fetch) tries to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
 ## Further Reading
 
 For more on EnvKey in general:

data/ext/{envkey-fetch_1.2.6_darwin_386 → envkey-fetch_1.2.9_darwin_amd64}/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright © 2017 Envkey Inc. <support@envkey.com>
+Copyright © 2021 Envkey Inc. <support@envkey.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/ext/{envkey-fetch_1.2.6_darwin_amd64 → envkey-fetch_1.2.9_darwin_amd64}/README.md

@@ -8,7 +8,7 @@ If you want to build an EnvKey library in a language that isn't yet officially s
 
 ## Installation
 
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
+envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this, as well as a [homebrew tap](https://github.com/envkey/homebrew-envkey)..
 
 **Install via bash:**
 
@@ -69,6 +69,13 @@ error: ENVKEY invalid
 -v, --version                 prints the version
 ```
 
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when `envkey-fetch` attempts to load your config. `envkey-fetch` tries to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
 ## Further Reading
 
 For more on EnvKey in general:

data/ext/{envkey-fetch_1.2.6_freebsd_386 → envkey-fetch_1.2.9_darwin_arm64}/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright © 2017 Envkey Inc. <support@envkey.com>
+Copyright © 2021 Envkey Inc. <support@envkey.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/ext/{envkey-fetch_1.2.6_darwin_386 → envkey-fetch_1.2.9_darwin_arm64}/README.md

@@ -8,7 +8,7 @@ If you want to build an EnvKey library in a language that isn't yet officially s
 
 ## Installation
 
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
+envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this, as well as a [homebrew tap](https://github.com/envkey/homebrew-envkey)..
 
 **Install via bash:**
 
@@ -69,6 +69,13 @@ error: ENVKEY invalid
 -v, --version                 prints the version
 ```
 
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when `envkey-fetch` attempts to load your config. `envkey-fetch` tries to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
 ## Further Reading
 
 For more on EnvKey in general:

data/ext/{envkey-fetch_1.2.6_freebsd_amd64 → envkey-fetch_1.2.9_freebsd_amd64}/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright © 2017 Envkey Inc. <support@envkey.com>
+Copyright © 2021 Envkey Inc. <support@envkey.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/ext/{envkey-fetch_1.2.6_freebsd_386 → envkey-fetch_1.2.9_freebsd_amd64}/README.md

@@ -8,7 +8,7 @@ If you want to build an EnvKey library in a language that isn't yet officially s
 
 ## Installation
 
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
+envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this, as well as a [homebrew tap](https://github.com/envkey/homebrew-envkey)..
 
 **Install via bash:**
 
@@ -69,6 +69,13 @@ error: ENVKEY invalid
 -v, --version                 prints the version
 ```
 
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when `envkey-fetch` attempts to load your config. `envkey-fetch` tries to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
 ## Further Reading
 
 For more on EnvKey in general:

data/ext/{envkey-fetch_1.2.6_darwin_amd64 → envkey-fetch_1.2.9_linux_amd64}/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright © 2017 Envkey Inc. <support@envkey.com>
+Copyright © 2021 Envkey Inc. <support@envkey.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/ext/{envkey-fetch_1.2.6_freebsd_amd64 → envkey-fetch_1.2.9_linux_amd64}/README.md

@@ -8,7 +8,7 @@ If you want to build an EnvKey library in a language that isn't yet officially s
 
 ## Installation
 
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
+envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this, as well as a [homebrew tap](https://github.com/envkey/homebrew-envkey)..
 
 **Install via bash:**
 
@@ -69,6 +69,13 @@ error: ENVKEY invalid
 -v, --version                 prints the version
 ```
 
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when `envkey-fetch` attempts to load your config. `envkey-fetch` tries to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
 ## Further Reading
 
 For more on EnvKey in general:

data/ext/envkey-fetch_1.2.9_windows_amd64/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright © 2021 Envkey Inc. <support@envkey.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/ext/envkey-fetch_1.2.9_windows_amd64/README.md

@@ -0,0 +1,97 @@
+# envkey-fetch
+
+This library contains [EnvKey](https://www.envkey.com)'s core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It accepts an `ENVKEY` generated by the [EnvKey App](https://www.github.com/envkey/envkey-app) and returns decrypted configuration for a specific app environment as json.
+
+It is used by EnvKey's various Client Libraries, including [envkey-source](https://github.com/envkey/envkey-source) for bash, [envkey-ruby](https://github.com/envkey/envkey-ruby) for Ruby and Rails, [envkey-python](https://github.com/envkey/envkey-python) for Python, [envkey-node](https://github.com/envkey/envkey-node) for Node.js, and [envkeygo](https://github.com/envkey/envkeygo) for Go.
+
+If you want to build an EnvKey library in a language that isn't yet officially supported, build some other type of integration, or simply play around with EnvKey on the command line, envkey-fetch is the library for you. If you just want to integrate EnvKey with your project, check out one of the aforementioned higher level libraries.
+
+## Installation
+
+envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this, as well as a [homebrew tap](https://github.com/envkey/homebrew-envkey)..
+
+**Install via bash:**
+
+```bash
+curl -s https://raw.githubusercontent.com/envkey/envkey-fetch/master/install.sh | bash
+```
+
+**Install manually:**
+
+Find the [release](https://github.com/envkey/envkey-fetch/releases) for your platform and architecture, and stick the appropriate binary somewhere in your `PATH` (or wherever you like really).
+
+**Install from source:**
+
+With Go installed, clone the project into your `GOPATH`. `cd` into the directory and run `go get` and `go build`.
+
+**Cross-compile from source:**
+
+To compile cross-platform binaries, make sure Go is installed, then install [goreleaser](https://goreleaser.com/) - follow instructions in the docs to do so.
+
+Then to cross-compile, run:
+
+`goreleaser`
+
+Binaries for each platform will be output to the `dist` folder.
+
+## Usage
+
+```bash
+envkey-fetch YOUR-ENVKEY [flags]
+```
+
+This will either write your the app environment's configuration associated with your `ENVKEY` as json to stdout or write an error message beginning with `error:` to stdout.
+
+### Example json output
+
+```json
+{"TEST":"it","TEST_2":"works!"}
+```
+
+### Example error output
+
+```text
+error: ENVKEY invalid
+```
+
+### Flags
+
+```text
+    --cache                   cache encrypted config as a local backup (default is false)
+    --cache-dir string        cache directory (default is $HOME/.envkey/cache)
+    --client-name string      calling client library name (default is none)
+    --client-version string   calling client library version (default is none)
+-h, --help                    help for envkey-fetch
+    --retries uint8           number of times to retry requests on failure (default 3)
+    --retryBackoff float      retry backoff factor: {retryBackoff} * (2 ^ {retries - 1}) (default 1)
+    --timeout float           timeout in seconds for http requests (default 10)
+    --verbose                 print verbose output (default is false)
+-v, --version                 prints the version
+```
+
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when `envkey-fetch` attempts to load your config. `envkey-fetch` tries to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
+## Further Reading
+
+For more on EnvKey in general:
+
+Read the [docs](https://docs.envkey.com).
+
+Read the [integration quickstart](https://docs.envkey.com/integration-quickstart.html).
+
+Read the [security and cryptography overview](https://security.envkey.com).
+
+## Need help? Have questions, feedback, or ideas?
+
+Post an [issue](https://github.com/envkey/envkey-fetch/issues) or email us: [support@envkey.com](mailto:support@envkey.com).
+
+
+
+
+
+

data/lib/envkey/platform.rb

@@ -37,12 +37,12 @@ module Envkey::Platform
   end
 
   def self.arch_part
-    # workaround for mac M1 chip until Go compiler supports it natively
-    # amd64 seems to work for now
     if platform_part == "darwin" && ARCH == "arm"
+      "arm64"
+    elsif ARCH == "x86_64"
       "amd64"
     else
-      ARCH == "x86_64" ? "amd64" : "386"
+      raise "As of 1.3.0, envkey-ruby only supports 64-bit systems. Please use an earlier version for 32-bit support."
     end
   end
 

data/lib/envkey/version.rb

@@ -1,4 +1,4 @@
 module Envkey
-  VERSION = "1.2.7"
-  ENVKEY_FETCH_VERSION="1.2.6"
+  VERSION = "1.3.0"
+  ENVKEY_FETCH_VERSION="1.2.9"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: envkey
 version: !ruby/object:Gem::Version
-  version: 1.2.7
+  version: 1.3.0
 platform: ruby
 authors:
 - Dane Schneider
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-02-02 00:00:00.000000000 Z
+date: 2021-04-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -83,30 +83,21 @@ files:
 - bin/console
 - bin/setup
 - envkey.gemspec
-- ext/envkey-fetch_1.2.6_darwin_386/LICENSE
-- ext/envkey-fetch_1.2.6_darwin_386/README.md
-- ext/envkey-fetch_1.2.6_darwin_386/envkey-fetch
-- ext/envkey-fetch_1.2.6_darwin_amd64/LICENSE
-- ext/envkey-fetch_1.2.6_darwin_amd64/README.md
-- ext/envkey-fetch_1.2.6_darwin_amd64/envkey-fetch
-- ext/envkey-fetch_1.2.6_freebsd_386/LICENSE
-- ext/envkey-fetch_1.2.6_freebsd_386/README.md
-- ext/envkey-fetch_1.2.6_freebsd_386/envkey-fetch
-- ext/envkey-fetch_1.2.6_freebsd_amd64/LICENSE
-- ext/envkey-fetch_1.2.6_freebsd_amd64/README.md
-- ext/envkey-fetch_1.2.6_freebsd_amd64/envkey-fetch
-- ext/envkey-fetch_1.2.6_linux_386/LICENSE
-- ext/envkey-fetch_1.2.6_linux_386/README.md
-- ext/envkey-fetch_1.2.6_linux_386/envkey-fetch
-- ext/envkey-fetch_1.2.6_linux_amd64/LICENSE
-- ext/envkey-fetch_1.2.6_linux_amd64/README.md
-- ext/envkey-fetch_1.2.6_linux_amd64/envkey-fetch
-- ext/envkey-fetch_1.2.6_windows_386/LICENSE
-- ext/envkey-fetch_1.2.6_windows_386/README.md
-- ext/envkey-fetch_1.2.6_windows_386/envkey-fetch.exe
-- ext/envkey-fetch_1.2.6_windows_amd64/LICENSE
-- ext/envkey-fetch_1.2.6_windows_amd64/README.md
-- ext/envkey-fetch_1.2.6_windows_amd64/envkey-fetch.exe
+- ext/envkey-fetch_1.2.9_darwin_amd64/LICENSE
+- ext/envkey-fetch_1.2.9_darwin_amd64/README.md
+- ext/envkey-fetch_1.2.9_darwin_amd64/envkey-fetch
+- ext/envkey-fetch_1.2.9_darwin_arm64/LICENSE
+- ext/envkey-fetch_1.2.9_darwin_arm64/README.md
+- ext/envkey-fetch_1.2.9_darwin_arm64/envkey-fetch
+- ext/envkey-fetch_1.2.9_freebsd_amd64/LICENSE
+- ext/envkey-fetch_1.2.9_freebsd_amd64/README.md
+- ext/envkey-fetch_1.2.9_freebsd_amd64/envkey-fetch
+- ext/envkey-fetch_1.2.9_linux_amd64/LICENSE
+- ext/envkey-fetch_1.2.9_linux_amd64/README.md
+- ext/envkey-fetch_1.2.9_linux_amd64/envkey-fetch
+- ext/envkey-fetch_1.2.9_windows_amd64/LICENSE
+- ext/envkey-fetch_1.2.9_windows_amd64/README.md
+- ext/envkey-fetch_1.2.9_windows_amd64/envkey-fetch.exe
 - lib/envkey.rb
 - lib/envkey/core.rb
 - lib/envkey/fetch.rb

data/ext/envkey-fetch_1.2.6_linux_386/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright © 2017 Envkey Inc. <support@envkey.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/ext/envkey-fetch_1.2.6_linux_386/README.md

@@ -1,90 +0,0 @@
-# envkey-fetch
-
-This library contains [EnvKey](https://www.envkey.com)'s core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It accepts an `ENVKEY` generated by the [EnvKey App](https://www.github.com/envkey/envkey-app) and returns decrypted configuration for a specific app environment as json.
-
-It is used by EnvKey's various Client Libraries, including [envkey-source](https://github.com/envkey/envkey-source) for bash, [envkey-ruby](https://github.com/envkey/envkey-ruby) for Ruby and Rails, [envkey-python](https://github.com/envkey/envkey-python) for Python, [envkey-node](https://github.com/envkey/envkey-node) for Node.js, and [envkeygo](https://github.com/envkey/envkeygo) for Go.
-
-If you want to build an EnvKey library in a language that isn't yet officially supported, build some other type of integration, or simply play around with EnvKey on the command line, envkey-fetch is the library for you. If you just want to integrate EnvKey with your project, check out one of the aforementioned higher level libraries.
-
-## Installation
-
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
-
-**Install via bash:**
-
-```bash
-curl -s https://raw.githubusercontent.com/envkey/envkey-fetch/master/install.sh | bash
-```
-
-**Install manually:**
-
-Find the [release](https://github.com/envkey/envkey-fetch/releases) for your platform and architecture, and stick the appropriate binary somewhere in your `PATH` (or wherever you like really).
-
-**Install from source:**
-
-With Go installed, clone the project into your `GOPATH`. `cd` into the directory and run `go get` and `go build`.
-
-**Cross-compile from source:**
-
-To compile cross-platform binaries, make sure Go is installed, then install [goreleaser](https://goreleaser.com/) - follow instructions in the docs to do so.
-
-Then to cross-compile, run:
-
-`goreleaser`
-
-Binaries for each platform will be output to the `dist` folder.
-
-## Usage
-
-```bash
-envkey-fetch YOUR-ENVKEY [flags]
-```
-
-This will either write your the app environment's configuration associated with your `ENVKEY` as json to stdout or write an error message beginning with `error:` to stdout.
-
-### Example json output
-
-```json
-{"TEST":"it","TEST_2":"works!"}
-```
-
-### Example error output
-
-```text
-error: ENVKEY invalid
-```
-
-### Flags
-
-```text
-    --cache                   cache encrypted config as a local backup (default is false)
-    --cache-dir string        cache directory (default is $HOME/.envkey/cache)
-    --client-name string      calling client library name (default is none)
-    --client-version string   calling client library version (default is none)
--h, --help                    help for envkey-fetch
-    --retries uint8           number of times to retry requests on failure (default 3)
-    --retryBackoff float      retry backoff factor: {retryBackoff} * (2 ^ {retries - 1}) (default 1)
-    --timeout float           timeout in seconds for http requests (default 10)
-    --verbose                 print verbose output (default is false)
--v, --version                 prints the version
-```
-
-## Further Reading
-
-For more on EnvKey in general:
-
-Read the [docs](https://docs.envkey.com).
-
-Read the [integration quickstart](https://docs.envkey.com/integration-quickstart.html).
-
-Read the [security and cryptography overview](https://security.envkey.com).
-
-## Need help? Have questions, feedback, or ideas?
-
-Post an [issue](https://github.com/envkey/envkey-fetch/issues) or email us: [support@envkey.com](mailto:support@envkey.com).
-
-
-
-
-
-

data/ext/envkey-fetch_1.2.6_linux_amd64/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright © 2017 Envkey Inc. <support@envkey.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/ext/envkey-fetch_1.2.6_linux_amd64/README.md

@@ -1,90 +0,0 @@
-# envkey-fetch
-
-This library contains [EnvKey](https://www.envkey.com)'s core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It accepts an `ENVKEY` generated by the [EnvKey App](https://www.github.com/envkey/envkey-app) and returns decrypted configuration for a specific app environment as json.
-
-It is used by EnvKey's various Client Libraries, including [envkey-source](https://github.com/envkey/envkey-source) for bash, [envkey-ruby](https://github.com/envkey/envkey-ruby) for Ruby and Rails, [envkey-python](https://github.com/envkey/envkey-python) for Python, [envkey-node](https://github.com/envkey/envkey-node) for Node.js, and [envkeygo](https://github.com/envkey/envkeygo) for Go.
-
-If you want to build an EnvKey library in a language that isn't yet officially supported, build some other type of integration, or simply play around with EnvKey on the command line, envkey-fetch is the library for you. If you just want to integrate EnvKey with your project, check out one of the aforementioned higher level libraries.
-
-## Installation
-
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
-
-**Install via bash:**
-
-```bash
-curl -s https://raw.githubusercontent.com/envkey/envkey-fetch/master/install.sh | bash
-```
-
-**Install manually:**
-
-Find the [release](https://github.com/envkey/envkey-fetch/releases) for your platform and architecture, and stick the appropriate binary somewhere in your `PATH` (or wherever you like really).
-
-**Install from source:**
-
-With Go installed, clone the project into your `GOPATH`. `cd` into the directory and run `go get` and `go build`.
-
-**Cross-compile from source:**
-
-To compile cross-platform binaries, make sure Go is installed, then install [goreleaser](https://goreleaser.com/) - follow instructions in the docs to do so.
-
-Then to cross-compile, run:
-
-`goreleaser`
-
-Binaries for each platform will be output to the `dist` folder.
-
-## Usage
-
-```bash
-envkey-fetch YOUR-ENVKEY [flags]
-```
-
-This will either write your the app environment's configuration associated with your `ENVKEY` as json to stdout or write an error message beginning with `error:` to stdout.
-
-### Example json output
-
-```json
-{"TEST":"it","TEST_2":"works!"}
-```
-
-### Example error output
-
-```text
-error: ENVKEY invalid
-```
-
-### Flags
-
-```text
-    --cache                   cache encrypted config as a local backup (default is false)
-    --cache-dir string        cache directory (default is $HOME/.envkey/cache)
-    --client-name string      calling client library name (default is none)
-    --client-version string   calling client library version (default is none)
--h, --help                    help for envkey-fetch
-    --retries uint8           number of times to retry requests on failure (default 3)
-    --retryBackoff float      retry backoff factor: {retryBackoff} * (2 ^ {retries - 1}) (default 1)
-    --timeout float           timeout in seconds for http requests (default 10)
-    --verbose                 print verbose output (default is false)
--v, --version                 prints the version
-```
-
-## Further Reading
-
-For more on EnvKey in general:
-
-Read the [docs](https://docs.envkey.com).
-
-Read the [integration quickstart](https://docs.envkey.com/integration-quickstart.html).
-
-Read the [security and cryptography overview](https://security.envkey.com).
-
-## Need help? Have questions, feedback, or ideas?
-
-Post an [issue](https://github.com/envkey/envkey-fetch/issues) or email us: [support@envkey.com](mailto:support@envkey.com).
-
-
-
-
-
-

data/ext/envkey-fetch_1.2.6_windows_386/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright © 2017 Envkey Inc. <support@envkey.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/ext/envkey-fetch_1.2.6_windows_386/README.md

@@ -1,90 +0,0 @@
-# envkey-fetch
-
-This library contains [EnvKey](https://www.envkey.com)'s core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It accepts an `ENVKEY` generated by the [EnvKey App](https://www.github.com/envkey/envkey-app) and returns decrypted configuration for a specific app environment as json.
-
-It is used by EnvKey's various Client Libraries, including [envkey-source](https://github.com/envkey/envkey-source) for bash, [envkey-ruby](https://github.com/envkey/envkey-ruby) for Ruby and Rails, [envkey-python](https://github.com/envkey/envkey-python) for Python, [envkey-node](https://github.com/envkey/envkey-node) for Node.js, and [envkeygo](https://github.com/envkey/envkeygo) for Go.
-
-If you want to build an EnvKey library in a language that isn't yet officially supported, build some other type of integration, or simply play around with EnvKey on the command line, envkey-fetch is the library for you. If you just want to integrate EnvKey with your project, check out one of the aforementioned higher level libraries.
-
-## Installation
-
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
-
-**Install via bash:**
-
-```bash
-curl -s https://raw.githubusercontent.com/envkey/envkey-fetch/master/install.sh | bash
-```
-
-**Install manually:**
-
-Find the [release](https://github.com/envkey/envkey-fetch/releases) for your platform and architecture, and stick the appropriate binary somewhere in your `PATH` (or wherever you like really).
-
-**Install from source:**
-
-With Go installed, clone the project into your `GOPATH`. `cd` into the directory and run `go get` and `go build`.
-
-**Cross-compile from source:**
-
-To compile cross-platform binaries, make sure Go is installed, then install [goreleaser](https://goreleaser.com/) - follow instructions in the docs to do so.
-
-Then to cross-compile, run:
-
-`goreleaser`
-
-Binaries for each platform will be output to the `dist` folder.
-
-## Usage
-
-```bash
-envkey-fetch YOUR-ENVKEY [flags]
-```
-
-This will either write your the app environment's configuration associated with your `ENVKEY` as json to stdout or write an error message beginning with `error:` to stdout.
-
-### Example json output
-
-```json
-{"TEST":"it","TEST_2":"works!"}
-```
-
-### Example error output
-
-```text
-error: ENVKEY invalid
-```
-
-### Flags
-
-```text
-    --cache                   cache encrypted config as a local backup (default is false)
-    --cache-dir string        cache directory (default is $HOME/.envkey/cache)
-    --client-name string      calling client library name (default is none)
-    --client-version string   calling client library version (default is none)
--h, --help                    help for envkey-fetch
-    --retries uint8           number of times to retry requests on failure (default 3)
-    --retryBackoff float      retry backoff factor: {retryBackoff} * (2 ^ {retries - 1}) (default 1)
-    --timeout float           timeout in seconds for http requests (default 10)
-    --verbose                 print verbose output (default is false)
--v, --version                 prints the version
-```
-
-## Further Reading
-
-For more on EnvKey in general:
-
-Read the [docs](https://docs.envkey.com).
-
-Read the [integration quickstart](https://docs.envkey.com/integration-quickstart.html).
-
-Read the [security and cryptography overview](https://security.envkey.com).
-
-## Need help? Have questions, feedback, or ideas?
-
-Post an [issue](https://github.com/envkey/envkey-fetch/issues) or email us: [support@envkey.com](mailto:support@envkey.com).
-
-
-
-
-
-

data/ext/envkey-fetch_1.2.6_windows_amd64/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright © 2017 Envkey Inc. <support@envkey.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/ext/envkey-fetch_1.2.6_windows_amd64/README.md

@@ -1,90 +0,0 @@
-# envkey-fetch
-
-This library contains [EnvKey](https://www.envkey.com)'s core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It accepts an `ENVKEY` generated by the [EnvKey App](https://www.github.com/envkey/envkey-app) and returns decrypted configuration for a specific app environment as json.
-
-It is used by EnvKey's various Client Libraries, including [envkey-source](https://github.com/envkey/envkey-source) for bash, [envkey-ruby](https://github.com/envkey/envkey-ruby) for Ruby and Rails, [envkey-python](https://github.com/envkey/envkey-python) for Python, [envkey-node](https://github.com/envkey/envkey-node) for Node.js, and [envkeygo](https://github.com/envkey/envkeygo) for Go.
-
-If you want to build an EnvKey library in a language that isn't yet officially supported, build some other type of integration, or simply play around with EnvKey on the command line, envkey-fetch is the library for you. If you just want to integrate EnvKey with your project, check out one of the aforementioned higher level libraries.
-
-## Installation
-
-envkey-fetch compiles into a simple static binary with no dependencies, which makes installation a simple matter of fetching the right binary for your platform and putting it in your `PATH`. An `install.sh` script is available to simplify this.
-
-**Install via bash:**
-
-```bash
-curl -s https://raw.githubusercontent.com/envkey/envkey-fetch/master/install.sh | bash
-```
-
-**Install manually:**
-
-Find the [release](https://github.com/envkey/envkey-fetch/releases) for your platform and architecture, and stick the appropriate binary somewhere in your `PATH` (or wherever you like really).
-
-**Install from source:**
-
-With Go installed, clone the project into your `GOPATH`. `cd` into the directory and run `go get` and `go build`.
-
-**Cross-compile from source:**
-
-To compile cross-platform binaries, make sure Go is installed, then install [goreleaser](https://goreleaser.com/) - follow instructions in the docs to do so.
-
-Then to cross-compile, run:
-
-`goreleaser`
-
-Binaries for each platform will be output to the `dist` folder.
-
-## Usage
-
-```bash
-envkey-fetch YOUR-ENVKEY [flags]
-```
-
-This will either write your the app environment's configuration associated with your `ENVKEY` as json to stdout or write an error message beginning with `error:` to stdout.
-
-### Example json output
-
-```json
-{"TEST":"it","TEST_2":"works!"}
-```
-
-### Example error output
-
-```text
-error: ENVKEY invalid
-```
-
-### Flags
-
-```text
-    --cache                   cache encrypted config as a local backup (default is false)
-    --cache-dir string        cache directory (default is $HOME/.envkey/cache)
-    --client-name string      calling client library name (default is none)
-    --client-version string   calling client library version (default is none)
--h, --help                    help for envkey-fetch
-    --retries uint8           number of times to retry requests on failure (default 3)
-    --retryBackoff float      retry backoff factor: {retryBackoff} * (2 ^ {retries - 1}) (default 1)
-    --timeout float           timeout in seconds for http requests (default 10)
-    --verbose                 print verbose output (default is false)
--v, --version                 prints the version
-```
-
-## Further Reading
-
-For more on EnvKey in general:
-
-Read the [docs](https://docs.envkey.com).
-
-Read the [integration quickstart](https://docs.envkey.com/integration-quickstart.html).
-
-Read the [security and cryptography overview](https://security.envkey.com).
-
-## Need help? Have questions, feedback, or ideas?
-
-Post an [issue](https://github.com/envkey/envkey-fetch/issues) or email us: [support@envkey.com](mailto:support@envkey.com).
-
-
-
-
-
-