polyn-cli 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4157c24284768c4e60893c3f3d7aca891e8916752ca85c6c48577ad59b9719bc
-  data.tar.gz: 114bb082e7f42f3db6d0efde45d4f058bb33bab652c42fc316668b6456d0e500
+  metadata.gz: a516676ead604b6dcfc242c75addef95ad9512f4c7a9b009369cb46d581f946e
+  data.tar.gz: 9ebdfaec0ba3df014121d75d9903ee234dad27ba4444d45178cdf66fd132336d
 SHA512:
-  metadata.gz: c349dfca556555beaccbe06d2829378e4fb027a76651d444b3f0b0b8560237ca4f2ab8a8678be12de69eee47ade4837ca8cae405e632fbc2c5e2a5e55cbbae0d
-  data.tar.gz: 1d09e688a62159910697b791de37cebbd0d21f5e7078b84201854b777e0b3d22bcf93b9f034fd4d81f9125ddd32a17d683c0e0d9284a360e0ddb2e23afdd4e99
+  metadata.gz: 545df32cdd3d928022e23798cbb08ee88521fc54248a1fd1911e80b88ff71d97987f092b2d73429942ec2fa66e818a8c0d88d11de30d7f5f77bd73ff3078e496
+  data.tar.gz: 58f0c9aaa9348efdf8c4310c1c1e7376cfb57d43e2f662015cbc224d14df0306ffc6da439f0618a079d08f57aeb3b08391b61cfa622ea5d1f8843fbd07989623

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    polyn-cli (0.1.3)
+    polyn-cli (0.1.4)
       dotenv (~> 2.7.6)
       json_schemer (~> 0.2)
       nats-pure (~> 2.0.0)

data/lib/polyn/cli/version.rb

@@ -2,6 +2,6 @@
 
 module Polyn
   class Cli
-    VERSION = "0.1.3"
+    VERSION = "0.1.4"
   end
 end

data/lib/polyn/cli.rb

@@ -130,7 +130,7 @@ module Polyn
 
       def tf_apply
         if polyn_env == "development"
-          %(terraform apply -var "jetstream_servers=#{nats_servers}")
+          %(terraform apply -auto-approve -input=false -var "jetstream_servers=#{nats_servers}")
         else
           "terraform apply -auto-approve -input=false "\
             "-var \"jetstream_servers=#{nats_servers}\" "\

data/lib/polyn/templates/README.md

@@ -3,20 +3,19 @@
 This repository contains all of the events and terraform resources for the Polyn services
 environment.
 
-## Development Setup
-
 1. Install [Ruby](https://github.com/asdf-vm/asdf-ruby)
-2. Install Terraform. For M1 Macs, [download the AMD64 version](https://www.terraform.io/downloads)
+2. Install bundler `gem install bundler`
+3. Install dependencies `bundle install`
+4. Install Terraform. For M1 Macs, [download the AMD64 version](https://www.terraform.io/downloads)
    rather than using Homebrew to install Terraform.
-3. Ensure Docker & Docker Compose is installed
-4. [Install the Polyn CLI](https://github.com/SpiffInc/polyn-cli)
-5. Call `polyn tf_init` if this is the first time using terraform in the codebase.
-6. Call `polyn up`. By default this will run in `development` mode, which will start the NATS
+5. Ensure Docker & Docker Compose is installed
+6. Call `bundle exec polyn tf_init` if this is the first time using terraform in the codebase.
+7. Call `bundle exec polyn up`. By default this will run in `development` mode, which will start the NATS
    server, configure it via Terraform, and update the Polyn Event Registry.
 
 ### Running NATS locally
 
-`polyn up` will use run a Docker container for you if one is not already running. Alternatively, you can run `nats-server` yourself locally if you prefer.
+`bundle exec polyn up` will use run a Docker container for you if one is not already running. Alternatively, you can run `nats-server` yourself locally if you prefer.
 
 ## Naming Conventions
 
@@ -24,15 +23,15 @@ See the Protocol Documentation for [Naming Conventions](https://github.com/Spiff
 
 ## Streams
 
-Each stream should have its own configuration file under `./tf` . Run `polyn gen:stream <stream_name>` to generate a new configuration file for a stream
+Each stream should have its own configuration file under `./tf`. Run `bundle exec polyn gen:stream <stream_name>` to generate a new configuration file for a stream
 
 ## Consumers
 
-Run `polyn gen:consumer <stream_name> <destination_name> <event_type>` to generate new configuration for a consumer of a stream. It will be included in the same file as the stream configuration.
+Run `bundle exec polyn gen:consumer <stream_name> <destination_name> <event_type>` to generate new configuration for a consumer of a stream. It will be included in the same file as the stream configuration.
 
 ## Event Schemas
 
-Run `polyn gen:schema <event_type>` to generate a new JSON Schema for an event
+Run `bundle exec polyn gen:schema <event_type>` to generate a new JSON Schema for an event
 
 All the schemas for your events should live in the `./events` directory.
 The name of your schema file should be the same as your event, but with `.json` at the end.
@@ -45,7 +44,7 @@ This means you only need to include the JSON Schema for the `data` portion of th
 
 If you'd like to organize your events by team ownership or some other convention, you can use subdirectories to do so. The full event type should still be part of the file name. You should also ensure there are not duplicate event types in different directories as only one schema can be defined per event type.
 
-You can generate a schema in a subdirectory like this: `polyn gen:schema some/nested/dir/widgets.created.v1`
+You can generate a schema in a subdirectory like this: `bundle exec polyn gen:schema some/nested/dir/widgets.created.v1`
 
 ## Schema Versioning
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: polyn-cli
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Jarod
@@ -9,7 +9,7 @@ authors:
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2022-08-23 00:00:00.000000000 Z
+date: 2022-08-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dotenv