Publish to RubyGems #10
Comments
|
Would love to see this get integrated as part of base ChefDK! |
|
👍 |
|
Yes Please! |
|
Not wanting to vendor this has also kept me from using it in |
|
+1 |
|
Yes we need this ASAP |
|
👍 ! |
|
We'd like to use this for some non-chef work, but as others have stated above, would prefer to use it as part of our Thanks! |
|
+1 |
|
Very nice! Life would be so much easier if it's integrated! |
|
+1 Please publish... it would demonstrate Chef's love of vmWare to customers if we could depend on this in ChefDK |
|
PRETTY PLEASE! ;) |
|
+1 |
|
👍 We have numerous uses for this in our in-house automation as well as integrations with other projects once packaging and publishing are complete. Please publish this to rubygems. |
|
+1 |
|
This would be MOST helpful to have as a Gem! |
|
please +1 |
|
This would be really helpful! |
|
+1 Need this |
|
+1 |
|
Another plead to get this published to rubygems. We can't properly test kitchen-vcenter which many large VMware customers are relying on without this. Not pushing this to Rubygems hurts many users. |
We use kitchen-vcenter and having this published to rubygems would be a HUGE help! |
|
Hi All, Please note, the new binding will not be backwards compatible with the existing binding and we will be providing updated samples and details on the Swagger integration. Additionally, we'll be looking at posting to gems.org following the transition. Please have a look and offer your feedback! Regards, |
I know everyone has already commented here, but I cant stress enough how amazing it would be to get this going for testing our chef cookbooks on our vmware environment! |
|
@strefethen the OpenAPI branch says the gem is available from rubygems.org, but it's not there. Can you confirm? I may be missing something... |
|
@jameswnl It's not currently. I updated the README to reflect the fact that that is the plan once this moves to |
|
thanks @jrgarcia for the clarification. |
|
I've merged the |

Please Please Please publish this to rubygems, so we can use it in our
gemspec. If you don't we will need to figure out a way to automatically pull this down, build it locally and inject into our integration.Thanks!
The text was updated successfully, but these errors were encountered: