trixie 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fe98b3f0bf37304b30f8128a4d9de6c42db4bbdae41054f1fd4f135003337a64
-  data.tar.gz: 4970d509ce2c73acaf0be36d7401179bc5a56461507306bd4789317ada2841e7
+  metadata.gz: 4601cd84921ad3fca11a80ffb627ef4b5d44d9a404dc25ac1905d75ab12a0b96
+  data.tar.gz: fcd3bb97d53845a6cd7752c90305bd9641c7809d57e86fc2d9fd4a6bcab41e96
 SHA512:
-  metadata.gz: 0a1cdb36ed57e082a2bec90c58e0f85d49a84a8ea0a926c0ca90b80e4a71c5b5a4e08431aa2b2c1ed98579b606960543a5d94ee3a2f2255404e7b6436bf68ab6
-  data.tar.gz: f65d4e4c2cd6aff21bb9fb4f0a049825ddc5dd148666769c3b4b0107513c08da4817ec232b6074e25cc7315bc36defc30646c14ec85f49b60a95a25366c77294
+  metadata.gz: 558dbef73b15724f9559e64d9f20cfa736fddea2445d8a9edd7c7a8bd9ee514a4c8a244356095c470787e509df6af58c29a99525bd96f5ef94d718a287e75852
+  data.tar.gz: 8327f5fa9e8392e563e888fd981760ac6ec78438de8a28cf8b0c83691c8748dcdb6fd6156457977132421e6780b157c1eae17d5ab59ffd9921486e3f6345d732

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    trixie (0.1.3)
+    trixie (0.1.4)
       dry-cli (~> 0.7.0)
       dry-schema (~> 1.10.0)
       dry-validation (~> 1.8.0)

data/README.md

@@ -18,7 +18,20 @@ secrets:
      value: "{{ op://Developers/NPM_TOKEN/SETUP_SECRET/value }}"
 ```
 
-Then you can run `trixie load > .env.secrets` to update your env file with the `NPM_TOKEN`
+Then you can run `trixie load > .env.secrets` to update your env file with the `NPM_TOKEN`.
+
+Alternatively, you can also leverage the following environment variables:
+- TRIXIE_OP_ADDRESS - sets the authentication address for 1Password
+- TRIXIE_OP_EMAIL - sets the user email address for 1Password
+
+Example:
+```ssh
+  TRIXIE_OP_ADDRESS=https://{account}.1password.com \
+  TRIXIE_OP_EMAIL=john.doe@email.com \
+  trixie load > .env.secrets
+```
+this will populate your env file with:
+`export NPM_TOKEN={toptals-read-only-npm-token}`
 
 ### Groups
 
@@ -70,8 +83,7 @@ Or install it yourself as:
 ## TODO IDEAS
 
 1. Support Multiple Backends/Password Managers, Trixie::Loader can be refactored to be an adapter for the op CLI
-2. Allow specific Backend options, eg: trixie load --backend op --backend-options '{ "email": "bar@foo.com",   "address": "foo.1password.com"}'
-3. Add a load --cache option, so fetched secrets could be retained for a while without using the Password Manager Backend
+2. Add a load --cache option, so fetched secrets could be retained for a while without using the Password Manager Backend
 
 ## Development
 

data/lib/trixie/load.rb

@@ -4,6 +4,8 @@ module Trixie
   # Fetches the specified secrets with op cli and returns them formatted
   class Load
     OP_NOT_INSTALLED = "op cli is not installed please download and install at https://developer.1password.com/docs/cli/get-started#install"
+    OP_ADDRESS_ENV = "TRIXIE_OP_ADDRESS"
+    OP_EMAIL_ENV = "TRIXIE_OP_EMAIL"
 
     def initialize(file:, groups: [], format: "env")
       @file = file
@@ -38,7 +40,7 @@ module Trixie
       warn "* Configuring 1password Account"
       warn "To get the Secret Key take a look at https://support.1password.com/secret-key/"
 
-      `op account add`
+      add_op_account
     end
 
     def fetch_secrets
@@ -58,5 +60,14 @@ module Trixie
     def formatted_secrets
       @formatter.call(filtered_secrets)
     end
+
+    def add_op_account
+      cmd = "op account add"
+
+      cmd += " --address #{ENV[OP_ADDRESS_ENV]}" if ENV[OP_ADDRESS_ENV]
+      cmd += " --email #{ENV[OP_EMAIL_ENV]}" if ENV[OP_EMAIL_ENV]
+
+      `#{cmd}`
+    end
   end
 end

data/lib/trixie/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Trixie
-  VERSION = "0.1.3"
+  VERSION = "0.1.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: trixie
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Toptal, LLC
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2022-11-08 00:00:00.000000000 Z
+date: 2022-12-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dry-cli