fig-lock 0.0.9 → 0.0.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fdf7b2e8a7f23e93d3ff059406fa5f9a9fdd621d
-  data.tar.gz: b8926d1ef7bbb4c26f4907b6d668147c33fe8485
+  metadata.gz: bf65230525cc94224a28ccc8387a29c5de3557d4
+  data.tar.gz: 7eaa81a30dc3a9611b8fb5a4ce22797a00d1d4b0
 SHA512:
-  metadata.gz: c51780e7a3dacd769a0e0466107a700f4f9843a9df67b23cfb99605eacef3794f66183984096f343dc6f9cc69eea329736371021a5af5bbc0122681526b8edf8
-  data.tar.gz: 2d472e31040f166b85d99fa5fa81bb56a527b115145250a5650aff8c7bfdf270429129b6e967f7fb4635aea6f14d84f7026af7a21ae093cf1b5abe5d95cf4230
+  metadata.gz: 3e5808866906d23d274d4c250a5c91a4e95ac7f147bde50431799b68e1e6ba755f6d51e7936f5d83999c1d77a30211fb81a20cc179e01d9b6f9bb506342937a6
+  data.tar.gz: 951e80d34a26d8a612e82027540a04694683a5881b04d8894a994122e1b911cae6a510e90a7e16baa96d23d4f1c589204fc3837c405fd22683a3fde9592ae1df

data/README.md

@@ -19,7 +19,7 @@ You want whatever *something* is to be versioned because versioning is important
 
 [Fig](http://orchardup.github.io/fig/index.html) lets you describe your images and how they interact. But if you use ```latest``` tags in your image (or really anything other than explicit version locking that you do manually by always using specific tags for your images), it doesn't help you keep track of your versions - it just uses whatever docker images are installed locally, or fetches the specific tags from registries. This approach is fine if you're dealing with images that don't change very often. But if you're working in an environment where several images in different source repositories are under heavy development, it can be a problem to have to manually update the fig.yml file, and integration tests that auto-update might not be feasible.
 
-This is why *Fig::Lock* exists. *Fig::Lock* lets you specify a fig.yml file containing images that use the ```latest``` tag. It generates fig.lock files by pulling down these images, figuring out what explicit tag latest maps to, and then generating a ```fig.lock``` file that uses these exact images. Then you can run your integration tests using this file, check it into source control, etc. The point is that you get a file that represents all the versions of the things in your system, so you can use this to reproduce it exactly.
+This is why *Fig::Lock* exists. *Fig::Lock* lets you specify a fig.yml file containing images that use the ```latest``` tag. It generates fig.lock files by figuring out what explicit tag these "latest" tags actually map to, and then generating a ```fig.lock``` file that uses these exact images. Then you can run your integration tests using this file, check it into source control, etc. The point is that you get a file that represents all the versions of the things in your system, so you can use this to reproduce it exactly.
 
 ## Installation
 

data/lib/fig/lock.rb

@@ -74,6 +74,7 @@ module Fig
 
       hash.each do |k,v|
         image = v['image']
+        continue unless image
         image = "#{image}:latest" unless image.index(':')
         log.info "Selecting latest tag for #{image} ..."
 

data/lib/fig/lock/version.rb

@@ -1,5 +1,5 @@
 module Fig
   class Lock
-    VERSION = "0.0.9"
+    VERSION = "0.0.10"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fig-lock
 version: !ruby/object:Gem::Version
-  version: 0.0.9
+  version: 0.0.10
 platform: ruby
 authors:
 - Michael Shea
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-07-03 00:00:00.000000000 Z
+date: 2014-07-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rest-client