hybrid_platforms_conductor 32.13.2 → 32.13.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1c395b236562cd49f9632e03fe36c11552a20bf5283136ea6653d8a800f4ca2e
-  data.tar.gz: 91d5237a9c854ac1ce42ceeacddcd64b00244c2cb077cd0a5d98a081e136799e
+  metadata.gz: 34bea5651c36db83740affa95f0bec53d48071a1f52b89b5bf9910a132ef0238
+  data.tar.gz: 47b80ca443cf040e7edafc33da4ca1a7f5346d5ae627156191c1acf01c8e54d3
 SHA512:
-  metadata.gz: fc33e7e4c055cc8dce0d9c84e623c6859fdcd4efb4ae3a3b8ad09b2e60d9109675da034c41e8846afc80e3328cd5d933c06273874d9757b9d263418f042a1ae2
-  data.tar.gz: 43e5f994c8946c3623f7718872df1e34c376a83dbcecec29e9d9322ca079b18fa75709f3b17f356e86c0d1ab03e98161c16cf4c095cc1fe39727097b1af3bb61
+  metadata.gz: 1278104d019860e8b9c014ed75309fa9635696db9c981c2c69a81f6bad61a366b5df9e44f70283484fecc8a05ff74550e1249f96462d15cf6a69eb7bfff9d9a1
+  data.tar.gz: 72f475a483d0d6c7315174a8b8e1f81588b25083460fd2294ba25e6f29596ddae84402eb7212fe6b8df2cc830c2c72d342e113a4b54a5999bb98d57d910bb4f5

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+# [v32.13.3](https://github.com/sweet-delights/hybrid-platforms-conductor/compare/v32.13.2...v32.13.3) (2021-05-07 10:09:33)
+
+### Patches
+
+* [Add section about benefits in doc](https://github.com/sweet-delights/hybrid-platforms-conductor/commit/23cd2b22244526e3b6705db0165f8a03e4dd88d8)
+
 # [v32.13.2](https://github.com/sweet-delights/hybrid-platforms-conductor/compare/v32.13.1...v32.13.2) (2021-05-06 15:47:14)
 
 ### Patches

data/README.md

@@ -35,7 +35,14 @@ Now being able to keep DevOps processes agile and robust is really difficult aro
 **This is where Hybrid Platforms Conductor can help: it helps DevOps define simple, robust and scalable processes that can adapt easily to ever-changing platforms and technologies in your development and operations environments.**
 
 In other words, Hybrid Platforms Conductor lets you **map your DevOps processes in a platform and technology independent way on simple interfaces** (CLI executables, APIs...).
-Having simple interfaces on your processes move the technical complexity in code instead of having it scattered around documentation becoming obsolete and increasing the learning curve.
+
+**Benefits** are multiple in terms of team organization and agility:
+* **Move the technical complexity** of your processes from scattered, duplicated and **diverging documentation to code that is effectively used**, maintained and tracked in a single place.
+* **Facilitate the adoption of new technologies and frameworks** in your team, without migrating previous ones, and keeping the same level of quality, robustness and agility of your DevOps processes.
+* **Scale easily whatever DevOps process** you have put in place for bigger platforms, bigger teams or more technologies.
+* **Decrease the learning curve** for newcomers in your team by having simple interfaces to be operated, whatever underlying tools and frameworks you are using behind.
+* Make sure **your DevOps processes apply easily to all the platforms** and organizations you want them to apply to.
+* Guarantee that you can **configure** each component of your platforms **in a deterministic and independent way**.
 
 ## How?
 

data/lib/hybrid_platforms_conductor/version.rb

@@ -1,5 +1,5 @@
 module HybridPlatformsConductor
 
-  VERSION = '32.13.2'
+  VERSION = '32.13.3'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hybrid_platforms_conductor
 version: !ruby/object:Gem::Version
-  version: 32.13.2
+  version: 32.13.3
 platform: ruby
 authors:
 - Muriel Salvan
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-05-06 00:00:00.000000000 Z
+date: 2021-05-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: range_operators