stacker_bee 2.1.1.pre247 → 2.1.1.pre248

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    ZTU4NzkwYjgxZGRjZTQ0MzBiMmY0Nzc2YThkMzRiYjA3ZGJmMzIyNw==
+    MjBiMThiYzYxY2JmYjVkMDgzYjdkZTRhZTcxNDlkZDYzZTgyNjg1Nw==
   data.tar.gz: !binary |-
-    OGJiOTIwNzY3ODM4NzBkNGRkNGVjNzNmN2UzMzgxNzM0NTBkYzZhMg==
+    MDFlOTdkMTgyOTQ1OGU0YWI5ODgyN2Q0YTFlYTA2MzA1OWIxZjI2Yg==
 SHA512:
   metadata.gz: !binary |-
-    MmVkYWNhOTQ1N2IxNDNhMTRkMWE3NzQyZmViM2Q1MTg3YWNjMzdmMGUyMDBh
-    MTc1OTNiNTAyMThkY2NhNmM4MmU4ZWQyNmM4NjJhNzZmZGM1YTYzY2ZiZDZj
-    NThhOTgzOGVmNDVmNTM4ODAzNmE4NWJmYTAyNDRhNzZhM2FkNmU=
+    ZDUzYzBiMjE2NTE3NGIzOGI4OTgzMWRlOTIyOTY4MWI5ZjJhZTY5MjNiYzU1
+    NGMxMThiYTRhMjhkNWE0MmVkOTkwYmEzYmMyNWY0YmE1Y2U2MTEyY2RlMTQ1
+    N2MzMDFhMDNjOTQxZTcwZjY2YTFhYTBlZjZmZWNjMmQyNzllNTg=
   data.tar.gz: !binary |-
-    MDkyNDVmZDhiOGZmMGI2OTU5YjQ5MjNjMGNhNGMwOTg5MGFiMzVhYmUxN2Ix
-    OTdiYTBhNzA0OGQwYmIzZWU1NzljNmI4NWZiZjY1MTY5MTcxMGE3MzkxOWJh
-    NGY0ZmUwZWI5Y2Y3YmU3YWE3YTc5ZGNmZGQyNTQ5MTAzNzc3YmE=
+    ZTA3MTRlNTdkOTc1MTA2MzlmOTYxYjliMzQwOTMxMDkzNWYzMjYzYjUwZWQx
+    YzRmY2RlMzRkODdiMGY4NTE0OGI4MWJjNDNkNzFjYjNlOWFhZTgzNWZkYjlm
+    M2UyNzI0NzNkYjk3MjlkMDRjODU0NTliYTkwMjFlZTJlZjczODA=

data/README.md

@@ -60,7 +60,7 @@ puts vm[:iso_display_text]
 For any endpoint requiring a map parameter, pass in a hash.
 
 ```ruby
-cloud_stack.create_tags(tags: { type: 'community' }, resource_type: "Template", resource_ids: id )
+cloud_stack.create_tags tags: { type: 'community' }, ...
 ```
 
 This will yield a request with the following query string:
@@ -206,6 +206,23 @@ StackerBee itself puts some middlewares on Faraday. Any middlewares you add will
 
 You can configure logging by passing in a logger object that adheres to the standard log4* logging conventions
 
+```ruby
+StackerBee::Client.configuration = {
+  logger: my_log4x_logger
+}
+```
+
+### SSL and `ssl_verify`
+
+StackerBee supports using SSL. To do so, use an HTTPS URL. In some deployments, CloudStack's SSL certificates don't match the DNS name that StackerBee will use to access it which will cause certificate validation errors. In these cases, if it's not feasible to fix the certificates (which is recommended) setting `ssl_verfiy` to `false` will cause StackerBee to ignore certificate validation errors.
+
+```ruby
+StackerBee::Client.configuration = {
+  url:        'https://my-cloudstack-server/client/api',
+  ssl_verify: false # ignore certificate validation errors
+}
+```
+
 ### Bulk Configuration
 
 The `StackerBee::Client` class can be configured with multiple options at once.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: stacker_bee
 version: !ruby/object:Gem::Version
-  version: 2.1.1.pre247
+  version: 2.1.1.pre248
 platform: ruby
 authors:
 - Greg Sterndale
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-07-03 00:00:00.000000000 Z
+date: 2014-07-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday