zeta 0.4.0 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: cc1fa795152d2eafcd724bf92624b98e6a24c3c0
-  data.tar.gz: de69bbd58d346f4d8d23243b5aa487cf4dd75443
+  metadata.gz: 688a5287b3424e9c923bbd1f9e118ae6b61c9546
+  data.tar.gz: c9e220790340b1abd33bd3fd1fa913bc9e9eef46
 SHA512:
-  metadata.gz: 26af9adcdd2b7a9de94f10a21261ad15a5ea3784c68cd05c462fbd3c64c5f0ab1a0bf2e279018ce8448b75f439b84706defc376467158738b1a908b09f204304
-  data.tar.gz: 49ade2a3d0b12551600eccd0599b91e6254d9deefeeca6f22a82158240ebf3e6225ba11500377dcc29680fc303cb3c6d6ca73e1a05e1812575a674914331774d
+  metadata.gz: ce397967dbcee851e5b438d88e360de94f5718adbb34b11efe8dac2c6fe98ade363a8751642cdf32ae3cbd2cdf86287171b712af45bb44ce4857877e0d9a49f0
+  data.tar.gz: ae3cbf5c2e485478ddb9c591ee223a36dd7cda9b291c8d9d7e179002f68897595af98fa2fa6a1bb1899a41a9ab1b983ae7b18ac09bf6afdf2731dcfa2679ebf5

data/CHANGELOG.markdown

@@ -1,3 +1,7 @@
+# 0.5.0 (02-Nov-15)
+- update lacerda
+- use lacerda stdout reporter by default
+
 # 0.4.0 (30-Oct-15)
 - update lacerda which uses ServiceName::Object in favor of ServiceName:Object
 

data/README.md

@@ -46,7 +46,7 @@ Each service has to contain two files in order for *Zeta* to do its job:
 These are simple markdown files in the wonderful [MSON](https://github.com/apiaryio/mson) format. Let's look at the contracts dir of **MessageService**, shall we?
 
 ### A publish specification:
-`contracts/publish.mson:`
+`contracts/publish.mson`:
 ```shell
 # Data Structures
 This file defines what MessageService may publish.
@@ -62,7 +62,7 @@ This file defines what MessageService may publish.
 So far so good. This way *MessageService* can tell the world what exactly it means when a `Message` object is published. Much the same, the *NotificationService* could define which properties of a `Message` object from the `MessageService` it is actually interested in:
 
 ### A consume specification:
-`contracts/consume.mson:`
+`contracts/consume.mson`:
 ```shell
 # Data Structures
 We just consume one object type, and it comes from the MessageService. Check it out!
@@ -75,7 +75,7 @@ We just consume one object type, and it comes from the MessageService. Check it
 As you can see, this consumer expects the `recipient_id` property to be present when a `Message` object is received from `MessageService`. While a publish specification just defines objects, a consume specification prefixes the names of objects it consumes with the name of the service publishing the object. As in our example above:
 
 ```
-# MessageService:Message
+# MessageService::Message
      |              `---------- object name
      `------------------------- service name
 
@@ -139,7 +139,7 @@ You typically just create the above file once in each project and then don't tou
 
 Here's how the infrastructure configuration file might look for our example above:
 
-`git@github.com:jensmander/zeta-config/infrastructure/master.yml:`
+`git@github.com:jensmander/zeta-config/infrastructure/master.yml`:
 ```yaml
 MessageService:
   github:
@@ -164,7 +164,7 @@ Whenever you add a service to the infrastructure, you just add it to this centra
 
 If your infrastruture configuration file is HTTP Basic auth protected, or in a private repository on github (that would be a good idea), make sure you `export HTTP_USER=username` and `HTTP_PASSWORD=secret` and *Zeta* will use that. If you host on github, the use your username and generate an API token to use as the password.
 
-### 4. Usage: Command line
+### 4. Usage: Without ruby (CLI)
 
 Zeta comes with a `zeta` command that takes care of all the things:
 
@@ -213,9 +213,9 @@ $ zeta -e development update_own_contracts validate
 
 Otherwise it will exit with an error and display any contract violations in JSON.
 
-### 5. Usage: in ruby
+### 5. Usage: With ruby
 
-If you use *Zeta* in ruby, it will automatically know the current service, i.e. the one that it's running in. It will create a singleton `Lacerda::Infrastructure` instance from the [Lacerda gem](https://github.com/moviepilot/Lacerda), which gives you access to a bunch of interesting functions. If you're using [pry](https://github.com/pry/pry), go ahead and do a quick `ls Zeta` and you will something like this, likely outdated, list:
+If you use *Zeta* in ruby, it will automatically know the current service, i.e. the one that it's running in. It will create a singleton `Lacerda::Infrastructure` instance from the [Lacerda gem](https://github.com/moviepilot/lacerda#readme), which gives you access to a bunch of interesting functions. If you're using [pry](https://github.com/pry/pry#readme), go ahead and do a quick `ls Zeta` and you will something like this, likely outdated, list:
 
 ```ruby
 [1] pry(main)> ls Zeta
@@ -231,6 +231,6 @@ Zeta.methods:
 Each and every one of these goes directly to your instance `Lacerda::Infrastructure`, as defined by `config/zeta.yml`. Feel free to explore them a bit, but the ones' that might be of most interest are:
 
 - `Zeta.validate_object_to_publish('Post', data_to_send)` makes sure that the content in `data_to_send` conforms to your 'Post' specification in your local `publish.mson`
-- `Zeta.consume_object('MessageService::Message', received_data)` will give you an instance of the [Blumquist](https://github.com/moviepilot/blumquist) class, which is an obect that has getters for all properties you specified in `consume.mson`
+- `Zeta.consume_object('MessageService::Message', received_data)` will give you an instance of the [Blumquist](https://github.com/moviepilot/blumquist#readme) class, which is an obect that has getters for all properties you specified in `consume.mson`
 
 If you use these in your servies, they will help keeping the publish and consume specifications in sync with what's actually happening in the code.

data/lib/zeta.rb

@@ -9,7 +9,8 @@ class Zeta
   # Not using the SingleForwardable module here so that, when
   # somebody tries to figure out how Zeta works by looking at
   # its methods, they don't get confused.
-  Zeta::Instance.instance_methods.each do |method|
+  methods = Zeta::Instance.instance_methods - Object.instance_methods
+  methods.each do |method|
     define_singleton_method method do |*args|
       send_args = [method, args].flatten.compact
       MUTEX.synchronize do

data/lib/zeta/instance.rb

@@ -42,7 +42,8 @@ class Zeta
     end
 
     def contracts_fulfilled?
-      infrastructure.contracts_fulfilled?
+      reporter = Lacerda::Reporters::Stdout.new(verbose: verbose?)
+      infrastructure.contracts_fulfilled?(reporter)
     end
 
     def infrastructure

data/lib/zeta/runner.rb

@@ -81,11 +81,8 @@ class Zeta::Runner
         puts "Validating your infrastructure with #{zeta.infrastructure.publishers.length} publishers and #{zeta.infrastructure.consumers.length} consumers..." if options[:verbose]
         zeta.contracts_fulfilled?
         unless zeta.errors.empty?
-          puts JSON.pretty_generate(zeta.errors)
-          puts "#{zeta.errors.length} contract violations".red
           exit(-1)
         end
-        puts "All contracts valid 🙌".green if options[:verbose]
       end
     rescue => e
       if options[:verbose]

data/lib/zeta/version.rb

@@ -1,3 +1,3 @@
 class Zeta
-  VERSION = "0.4.0"
+  VERSION = "0.5.0"
 end

data/zeta.gemspec

@@ -19,7 +19,7 @@ Gem::Specification.new do |spec|
   spec.require_paths = ['lib']
 
   spec.add_runtime_dependency 'rake', '~> 10.2'
-  spec.add_runtime_dependency 'lacerda', '~> 0.7'
+  spec.add_runtime_dependency 'lacerda', '~> 0.8'
   spec.add_runtime_dependency 'activesupport'
   spec.add_runtime_dependency 'httparty', '~> 0.13'
   spec.add_runtime_dependency 'colorize'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zeta
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.5.0
 platform: ruby
 authors:
 - Jannis Hermanns
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-30 00:00:00.000000000 Z
+date: 2015-11-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -30,14 +30,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.7'
+        version: '0.8'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.7'
+        version: '0.8'
 - !ruby/object:Gem::Dependency
   name: activesupport
   requirement: !ruby/object:Gem::Requirement