inprovise 0.2.25 → 0.2.26

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: b0c39cd5641b1b6344caaa037b2a17e101ce6916
-  data.tar.gz: 490cc558026a8d344a4c7b173a3f79331eebd5a4
+SHA256:
+  metadata.gz: f1d82e40d8838f046b9da3215bda4199e3eea1cd8229d4b7372f15846813e47d
+  data.tar.gz: 303717b5beceec1c601973bed73709e2899bd4aa266b2758905628bda1946499
 SHA512:
-  metadata.gz: ae32e1c77dc222f6e8d269a5bbc08474128a48cee76f0aee05d6cea312ab59b8145f6f256ea880c0e16ddda39bda252e85538453c449201f310ac2f6e58abc87
-  data.tar.gz: af419012a18a010c153b54487c67d4939645db0498da5e4f1218f1515bbd02f768dd25075e366971a6f68a320add8cb8f4c6c2f08eb8531b1f7890990dd2c814
+  metadata.gz: 1092284c11fcbf3ef25fa2118ac76ed20292c07cf0540a96feccff9cfab83a652eb98b1a429e707c97ec11c35a0eea46216d25ebab0aa894e6c3eaafd6836b31
+  data.tar.gz: c7298371106a5f199a7d80b8bd343444493ce7f862c164bbc7d261b59ba88b351753824db6e4455c799f8e21e642c2a5f92aea0a647ad0869cab6229e01f8a68

data/README.md

@@ -2,7 +2,7 @@
 Inprovise
 =========
 
-**Because provisioning small computing infrastructures should be simple, intuitive and NOT require additional infrastructure or elaborate setups just to run your provisioning scripts.** 
+**Because provisioning small computing infrastructures should be simple, intuitive and NOT require additional infrastructure or elaborate setups just to run your provisioning scripts.**
 
 Inprovise (Intuitive Provisioning Environment) is a super simple way to provision servers and virtual machines.
 
@@ -11,23 +11,23 @@ Inprovise (Intuitive Provisioning Environment) is a super simple way to provisio
 [![Test Coverage](https://codeclimate.com/github/mcorino/Inprovise/badges/coverage.png)](https://codeclimate.com/github/mcorino/Inprovise/coverage)
 [![Gem Version](https://badge.fury.io/rb/inprovise.png)](https://badge.fury.io/rb/inprovise)
 
-If you've found yourself stuck in the gap between deployment tools like Capistrano and full blown infrastructure tools like Puppet and Chef then Inprovise might be a good fit for you. 
-This is especially the case if you choose to cycle machines and prefer baking from scratch when changes are required rather than attempting to converge system state 
+If you've found yourself stuck in the gap between deployment tools like Capistrano and full blown infrastructure tools like Puppet and Chef then Inprovise might be a good fit for you.
+This is especially the case if you choose to cycle machines and prefer baking from scratch when changes are required rather than attempting to converge system state
 (although Inprovise is flexible and extensible enough to achieve anything you would like).
 
 Acknowledgement
 ---------------
 
-First off a very big acknowledgement.
-When searching (yet again) for a usable (as in 'easy' and 'intuitive') tool for managing the provisioning of our smallish computing farm 
+First off a very big acknowledgment.
+When searching (yet again) for a usable (as in 'easy' and 'intuitive') tool for managing the provisioning of our smallish computing farm
 (consisting of <10 host servers each running 6-12 VMs each) and yet again becoming disappointed by the requirements and overkill offered by tools like
 Chef and Puppet, I finally found the *Orca* tool by Andy Kent (https://github.com/andykent/orca).
 *This* was what I was thinking of!
 
-Unfortunately Andy some time ago deprecated his project and there were some aspects of Orca I did not really like (a major one being the definition of the infrastructure nodes and groups inside the provisioning schemes) 
+Unfortunately Andy some time ago deprecated his project and there were some aspects of Orca I did not really like (a major one being the definition of the infrastructure nodes and groups inside the provisioning schemes)
 as well as some missing bits (like more flexibility in the platform support).
-I really did like the agent-less setup and the simple and elegant structure of the DSL though as well as the fact it was written in one of my favorite programming languages. As Andy's arguments for discontinuing 
-did not apply to us I decided to take up his code and rework it to my ideas and provide it with a minimum of multi platform support to also be able to manage the non-*nix nodes we needed to provision. 
+I really did like the agent-less setup and the simple and elegant structure of the DSL though as well as the fact it was written in one of my favorite programming languages. As Andy's arguments for discontinuing
+did not apply to us I decided to take up his code and rework it to my ideas and provide it with a minimum of multi platform support to also be able to manage the non-*nix nodes we needed to provision.
 
 As Andy indicated the Orca name was (to be) handed over to another gem maintainer and I did not particularly like it anyway (sorry Andy) I renamed the package. Andy's code proved quite resilient to my changes
 though and (apart from the name changes) I was able to copy large chunks more or less verbatim and rework those step by step thereby increasing my coding production significantly.
@@ -45,25 +45,25 @@ All too often you need to get a new server up and running to a known state so th
 Inprovise fills the rather large gap between (2) and (3). It's a bigger gap then you think as both Puppet and Chef require...
 
 - bootstrapping a machine to a point where you are able to run them
-- Creating a seperate repository describing the configuration you require
+- Creating a separate repository describing the configuration you require
 - learning their complex syntaxes and structures
 - hiding the differences of different host OSes
 
 Inprovise fixes these problems by...
 
 - working directly over standardized protocols (SSH by default), all you need is a box that you can connect to
-- Inprovise maintains a simple (JSON) file based registry of your infrastructure  
+- Inprovise maintains a simple (JSON) file based registry of your infrastructure
 - scripting definitions can all go in a single file (although Inprovise supports modularization) and most servers can be configured in ~50 lines
 - scripts are defined in a ruby based DSL that consists of a very small number of basic commands to learn
 - Inprovise only requires a minimum operations (for cmd execution and file management) to be supported for any OS the details of which are abstracted through configurable handlers
 - apart from the protocol and minimal operation set Inprovise makes no assumptions about the underlying OS
-- Inprovise is extensible and adding platform specific features like package manager support can be achieved in a small amount of code using the core support 
+- Inprovise is extensible and adding platform specific features like package manager support can be achieved in a small amount of code using the core support
 
 
 What problems is Inprovise avoiding?
 -------------------------------
 
-Inprovise intentionally skirts around some important things that may or may not matter to you. 
+Inprovise intentionally skirts around some important things that may or may not matter to you.
 If they do then you are probably better using tools such as Puppet or Chef.
 
 Inprovise doesn't...
@@ -143,8 +143,8 @@ The Inprovise DSL
 Inprovise provides a Ruby based DSL to write your provisioning specifications. Files containing these provisioning
 specs are called `schemes`.
 Inprovise provisioning schemes are pure Ruby code and should preferably be stored in files with the '.rb' extension. When
-no scheme is specified Inprovise looks for the scheme `inprovise.rb` in the projects root (where the `infa.json` is located) by default. 
-Scheme scripts are really simple to learn in less than 5 mins. Below is an example inprovise.rb file with some hints to help you get started. 
+no scheme is specified Inprovise looks for the scheme `inprovise.rb` in the projects root (where the `infa.json` is located) by default.
+Scheme scripts are really simple to learn in less than 5 mins. Below is an example inprovise.rb file with some hints to help you get started.
 A more complete WIP example can be found in this gist... https://gist.github.com/andykent/5814997
 
 ````ruby
@@ -185,7 +185,7 @@ to contain pure Ruby code and is loaded as such. You can use this to require and
 scripts defined in your project's scheme files.
 
 As the scheme files themselves are also pure Ruby code you can also put configuration code there if that suites your use case better (for example if certain settings
-should only be available to scripts defined in one particular scheme file).  
+should only be available to scripts defined in one particular scheme file).
 
 Extensions
 ----------

data/lib/inprovise/sniffer/linux.rb

@@ -30,7 +30,7 @@ Inprovise::Sniffer.define('linux', false) do
       binary_exists?('dnf') ? 'dnf' : 'yum'
       when 'linuxmint', 'ubuntu', 'debian'
       'apt'
-      when /suse/
+      when 'suse', 'sles'
       'zypper'
     end
   end
@@ -41,7 +41,7 @@ Inprovise::Sniffer.define('linux', false) do
         when /RedHat/i
         'rhel'
         when /SUSE/i
-        run("#{bin} -d").chomp =~ /opensuse/i ? 'opensuse' : 'suse'
+        run("#{bin} -d").chomp =~ /opensuse/i ? 'suse' : 'sles'
         else
         distro.downcase
       end

data/lib/inprovise/version.rb

@@ -5,6 +5,6 @@
 
 module Inprovise
 
-  VERSION = '0.2.25'
+  VERSION = '0.2.26'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: inprovise
 version: !ruby/object:Gem::Version
-  version: 0.2.25
+  version: 0.2.26
 platform: ruby
 authors:
 - Martin Corino
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-02-25 00:00:00.000000000 Z
+date: 2018-06-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: colored
@@ -170,7 +170,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.8
+rubygems_version: 2.7.7
 signing_key: 
 specification_version: 4
 summary: Simple, easy and intuitive infrastructure provisioning