envkey 1.3.2 → 2.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: db0162afe84d50b0134a360d1b5e8f11ca6a5234
-  data.tar.gz: 50d82bdf211ae4ffe376a8ba19eb343dfdec5111
+SHA256:
+  metadata.gz: 74a2508e48707fe503cb1dfa48e12d9f8bf1d1901e2c34c16923ade03e5a7134
+  data.tar.gz: f29d0a246f9638060802b1c254bc3d5ecbcaf2a85156c0529da24b771ee31817
 SHA512:
-  metadata.gz: 957daed9c3cdd69ce06fa363d103df4654456e450b146bf880b3daf313373e6580b498eb4f7d8f6056d7cd3bb4acc66fe11fd5e1a15a9055e45a18cc221be562
-  data.tar.gz: 5edae58e1e8061536605036bc5f0cb2a5c21a278ddf54b8793a40e2a7cb7899e02155cf4eeb0ea057c4570a6854e06ec75865a1662430c2cdfb6800463ac5494
+  metadata.gz: 149bc05167ed64bd9b883e64374bfbd2ddfb42b1102dac19ff325e50cd6acf8c0c92b69401d2e20c1874e89f1c0421566bbc60524beb7e100c0e4df1fa85a88b
+  data.tar.gz: 0eb701bdbdd2b29b0280c6f746b2f84cc51e5e601280e0fd81dd480c4fe26d33399b99221419b4f5f8d8822c05da949b9815f11f2d9dcc7fa5f530e85ea796a4

data/.gitignore

@@ -1,3 +1,4 @@
+/ext/
 /.bundle/
 /.yardoc
 /Gemfile.lock
@@ -8,4 +9,6 @@
 /spec/reports/
 /tmp/
 *.gem
-.byebug_history
+.byebug_history
+
+*.version.shasum

data/envkey.gemspec

@@ -9,7 +9,7 @@ Gem::Specification.new do |spec|
   spec.authors       = ["Dane Schneider"]
   spec.email         = ["dane@envkey.com"]
 
-  spec.summary       = "Envkey secures and simplifies app secrets and config."
+  spec.summary       = "Envkey secures and simplifies configuration and secrets management."
   spec.homepage      = "https://www.envkey.com"
   spec.license       = "MIT"
 
@@ -22,9 +22,9 @@ Gem::Specification.new do |spec|
       "public gem pushes."
   end
 
-  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+  spec.files         = (`git ls-files -z`.split("\x0").reject do |f|
     f.match(%r{^(test|spec|features)/})
-  end
+  end).concat(["ext"])
   spec.bindir        = "exe"
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
@@ -32,6 +32,4 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "bundler", "~> 1.13"
   spec.add_development_dependency "rake", "~> 10.0"
   spec.add_development_dependency "rspec", "~> 3.0"
-
-  spec.add_runtime_dependency "dotenv", "~> 2.0"
 end

data/lib/envkey/core.rb

@@ -1,4 +1,3 @@
-require 'dotenv'
 require 'set'
 require 'json'
 require 'envkey/fetch'
@@ -7,50 +6,28 @@ module Envkey::Core
 
   def self.load_env
     original_env = ENV.to_h
-    dotenv_vars = Dotenv.parse
-
-    overwrite_dotenv_vars = JSON.parse(ENV["__ENVKEY_DOT_ENV_VARS"] || "[]")
     overwrite_envkey_vars = JSON.parse(ENV["__ENVKEY_VARS"] || "[]")
 
-    updated_dotenv_vars = dotenv_vars.keys.select do |k|
-      (overwrite_dotenv_vars.include?(k) || original_env[k] == nil)
-    end
-    updated_dotenv_vars.each do |k|
-      ENV[k] = dotenv_vars[k]
-    end
-
-    key = ENV["ENVKEY"]
-
-    # handle changed ENVKEY
-    if key && updated_dotenv_vars.include?("ENVKEY") && key != original_env["ENVKEY"]
-      overwrite_envkey_vars.each {|var| ENV.delete(var) }
-    end
-
-    if (key = ENV["ENVKEY"])
-      res = Envkey::Fetch.fetch_env(key)
-      if res && res.gsub("\n","").gsub("\r", "") != "" && !res.start_with?("error:")
-        envs = JSON.parse(res)
-        updated_envkey_vars = []
-        envs.each do |k,v|
-          var = k.upcase
-          if !ENV[var] || overwrite_envkey_vars.include?(var)
-            updated_envkey_vars << var
-            ENV[var] = v
-          end
+    res = Envkey::Fetch.fetch_env
+    if res && res.gsub("\n","").gsub("\r", "") != "" && !res.start_with?("error:")
+      envs = JSON.parse(res)
+      updated_envkey_vars = []
+      envs.each do |k,v|
+        var = k.upcase
+        if !ENV[var] || overwrite_envkey_vars.include?(var)
+          updated_envkey_vars << var
+          ENV[var] = v
         end
+      end
 
-        ENV["__ENVKEY_DOT_ENV_VARS"] = updated_dotenv_vars.to_json
-        ENV["__ENVKEY_VARS"] = updated_envkey_vars.to_json
+      ENV["__ENVKEY_VARS"] = updated_envkey_vars.to_json
 
-        return updated_dotenv_vars, updated_envkey_vars
-      elsif res.start_with?("error:")
-        STDERR.puts "envkey-fetch " + res
-        raise "ENVKEY invalid. Couldn't load vars."
-      else
-        raise "ENVKEY invalid. Couldn't load vars."
-      end
+      return updated_envkey_vars
+    elsif res.start_with?("error:")
+      STDERR.puts "envkey-source " + res
+      raise "ENVKEY invalid. Couldn't load vars."
     else
-      raise "ENVKEY missing - must be set as an environment variable or in a gitignored .env file in the root of your project. Go to https://www.envkey.com if you don't know what an ENVKEY is."
+      raise "ENVKEY invalid. Couldn't load vars."
     end
   end
 

data/lib/envkey/fetch.rb

@@ -2,16 +2,20 @@ require 'envkey/platform'
 
 module Envkey::Fetch
 
-  def self.fetch_env key
+  def self.fetch_env
     fetch_env_path = Envkey::Platform.fetch_env_path
-    `#{fetch_env_path} #{key}#{is_dev ? ' --cache' : ''} --client-name envkey-ruby --client-version #{Envkey::VERSION} 2>&1`
+    `#{fetch_env_path} --json#{should_cache ? ' --cache' : ''} --client-name envkey-ruby --client-version #{Envkey::VERSION} 2>&1`
+  end
+
+  def self.should_cache
+    is_dev || ENV["ENVKEY_SHOULD_CACHE"]
   end
 
   def self.is_dev
     dev_vals = %w(development test)
     dev_vals.include?(ENV["RAILS_ENV"]) ||
       dev_vals.include?(ENV["RACK_ENV"]) ||
-      (ENV["RAILS_ENV"].nil? && ENV["RACK_ENV"].nil? && File.exist?(".env"))
+      (ENV["RAILS_ENV"].nil? && ENV["RACK_ENV"].nil?)
   end
 
 end

data/lib/envkey/platform.rb

@@ -51,11 +51,11 @@ module Envkey::Platform
   end
 
   def self.fetch_env_path
-    File.expand_path("../../ext/#{lib_file_dir}/envkey-fetch#{ext}", File.dirname(__FILE__))
+    File.expand_path("../../ext/#{lib_file_dir}/envkey-source#{ext}", File.dirname(__FILE__))
   end
 
   def self.lib_file_dir
-    ["envkey-fetch", Envkey::ENVKEY_FETCH_VERSION.to_s, platform_part, arch_part].join("_")
+    ["envkey-source", Envkey::ENVKEY_SOURCE_VERSION.to_s, platform_part, arch_part].join("_")
   end
 
 end

data/lib/envkey/version.rb

@@ -1,4 +1,4 @@
 module Envkey
-  VERSION = "1.3.2"
-  ENVKEY_FETCH_VERSION="1.2.9"
+  VERSION = "2.0.7"
+  ENVKEY_SOURCE_VERSION = "2.0.23"
 end

data/sdkruby-version.txt

@@ -0,0 +1 @@
+2.0.6

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: envkey
 version: !ruby/object:Gem::Version
-  version: 1.3.2
+  version: 2.0.7
 platform: ruby
 authors:
 - Dane Schneider
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2022-02-02 00:00:00.000000000 Z
+date: 2022-04-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -52,21 +52,7 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '3.0'
-- !ruby/object:Gem::Dependency
-  name: dotenv
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.0'
-description: 
+description:
 email:
 - dane@envkey.com
 executables: []
@@ -78,41 +64,23 @@ files:
 - ".travis.yml"
 - Gemfile
 - LICENSE.txt
-- README.md
 - Rakefile
 - bin/console
 - bin/setup
 - envkey.gemspec
-- 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_linux_arm64/LICENSE
-- ext/envkey-fetch_1.2.9_linux_arm64/README.md
-- ext/envkey-fetch_1.2.9_linux_arm64/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
 - lib/envkey/platform.rb
 - lib/envkey/rails.rb
 - lib/envkey/version.rb
+- sdkruby-version.txt
 homepage: https://www.envkey.com
 licenses:
 - MIT
 metadata:
   allowed_push_host: https://rubygems.org
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -127,9 +95,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.14
-signing_key: 
+rubygems_version: 3.1.2
+signing_key:
 specification_version: 4
-summary: Envkey secures and simplifies app secrets and config.
+summary: Envkey secures and simplifies configuration and secrets management.
 test_files: []

data/README.md

@@ -1,86 +0,0 @@
-# envkey gem
-
-Integrate [EnvKey](https://www.envkey.com) with your Ruby or Ruby On Rails projects to keep api keys, credentials, and other configuration securely and automatically in sync for developers and servers.
-
-## Installation
-
-In your Gemfile:
-
-```ruby
-gem 'envkey'
-```
-
-If you're using Rails, that's all you need. In plain Ruby, you need to require envkey at the entry point of your application.
-
-```ruby
-require 'envkey'
-```
-
-## Usage
-
-Generate an `ENVKEY` in the [EnvKey App](https://github.com/envkey/envkey-app). Then set `ENVKEY=...`, either in a gitignored `.env` file in the root of your project (in development) or in an environment variable (on servers).
-
-Now all your EnvKey variables will be available on `ENV`.
-
-### Errors
-
-The gem will throw an error if an `ENVKEY` is missing or invalid.
-
-### Example
-
-Assume you have `STRIPE_SECRET_KEY` set to `sk_test_2a33b045e998d2ef60c7861d2ac22ea8` for the `development` environment in the EnvKey App. You generate a local development `ENVKEY`.
-
-In your project's **gitignored** `.env` file:
-
-```bash
-# .env
-ENVKEY=GsL8zC74DWchdpvssa9z-nk7humd7hJmAqNoA
-```
-
-In `config/initializers/stripe.rb`:
-
-```ruby
-Stripe.api_key = ENV.fetch("STRIPE_SECRET_KEY")
-```
-
-Now `STRIPE_SECRET_KEY` will stay automatically in sync for all the developers on your team.
-
-For a server, generate a server `ENVKEY` in the EnvKey App, then set the `ENVKEY` as an environment variable instead of putting it in a `.env` file.
-
-Now your servers will stay in sync as well. If you need to rotate your `STRIPE_SECRET_KEY` you can do it in a few seconds in the EnvKey App, restart your servers, and you're good to go. All your team's developers and all your servers will have the new value.
-
-### Overriding Vars
-
-The envkey gem will not overwrite existing environment variables or additional variables set in a `.env` file. This can be convenient for customizing environments that otherwise share the same configuration. You can also use [sub-environments](https://blog.envkey.com/development-staging-production-and-beyond-85f26f65edd6) in the EnvKey app for this purpose.
-
-### Working Offline
-
-The envkey gem caches your encrypted config in development so that you can still use it while offline. Your config will still be available (though possibly not up-to-date) the next time you lose your internet connection. If you do have a connection available, envkey will always load the latest config. Your cached encrypted config is stored in `$HOME/.envkey/cache`
-
-For caching purposes, the gem assumes you're in development mode if either `ENV["RAILS_ENV"]` or `ENV["RACK_ENV"]` is `"development"` or `"test"`. If you aren't using Rails or Rack, then it's assumed you're in development mode when a `.env` file exists in the root of your project.
-
-## envkey-fetch binaries
-
-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:
-
-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-ruby/issues) or email us: [support@envkey.com](mailto:support@envkey.com).
-

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

@@ -1,21 +0,0 @@
-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_darwin_amd64/README.md

@@ -1,97 +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, 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/ext/envkey-fetch_1.2.9_darwin_arm64/LICENSE

@@ -1,21 +0,0 @@
-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_darwin_arm64/README.md

@@ -1,97 +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, 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/ext/envkey-fetch_1.2.9_freebsd_amd64/LICENSE

@@ -1,21 +0,0 @@
-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_freebsd_amd64/README.md

@@ -1,97 +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, 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/ext/envkey-fetch_1.2.9_linux_amd64/LICENSE

@@ -1,21 +0,0 @@
-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_linux_amd64/README.md

@@ -1,97 +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, 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/ext/envkey-fetch_1.2.9_linux_arm64/LICENSE

@@ -1,21 +0,0 @@
-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_linux_arm64/README.md

@@ -1,97 +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, 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/ext/envkey-fetch_1.2.9_windows_amd64/LICENSE

@@ -1,21 +0,0 @@
-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

@@ -1,97 +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, 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).
-
-
-
-
-
-