brpm_content_framework 0.1.58 → 0.1.59

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NWI4OGQyZDQ3NzdiNjgzNTQ2YTNhMDllYTg0ZGVjMjQyNzdlYWNiNQ==
+    NzIzOTUzOTY3ZWU0NGUyYmY1NmFkNDg4MzE0Y2VmZTk5NWJlZDFhNA==
   data.tar.gz: !binary |-
-    ZThlZTExZjIzMTc3ZTNhNzYyMDA5MTZhYTcyNzc5NTRmMjhkMjcwYw==
+    ODUyN2Q0NGM1NzdiYjVmYTY2YzVhMThmNDJiMDg1ZWE4YmNmZWJmYg==
 SHA512:
   metadata.gz: !binary |-
-    NjQ3MWYyZGMxMjZhNDQxYjkxMzBkMjkxOGEzMGIyYzAwNzdmMTQyMGVlODg3
-    N2FkZTQ3OTljMzMxMThmN2FkNDhjMzc1YjdlZmQwZmFiOTVhODBjNWZmODJl
-    OWJjOWUxZGJlY2Y5YTYzOTJmZjRhZTcyNDNlY2ZhZDVkNjdlYjA=
+    M2Q3MmVkMWU0NTlkNzI2MTZkNTY3ZjZlYzQyZWI4M2VlNmFhNDliYTU2ZDU1
+    MjE5Nzg5ZmZkZDdlOTkxNWRhOTVlZmQ0N2IxMzMxYzlmYjcxODE2OTNmNDMy
+    ZjkzNzI5ODhiZDk3YmE0YmJjNjFkNzYxMjkyZjMyZTlkNWI2NDg=
   data.tar.gz: !binary |-
-    YmQ3ODk1MzE0Njg5ZjdiMDhlODhjZjc4MDQ1MzE3M2Q4NzJiMTNlYTZmNTA5
-    MTlhOTE5MzEwYmJjOTQ1YWE0Y2NiNGYwN2JkNDAwOWE2N2U4MmZiNzJkMmVj
-    MGZkOWRmOWNkZWYxZTM4OTE4N2YwZGJhYTIyNzkyNWU5MWI0MjU=
+    MjY3ZWRmMTc3OTMzZGViODNlYzA2YjgxYWYzMjBlZGQ4NjQ5ZmUwNzEwNTkx
+    YjljODQ2NzNjOTZjMDQzODQzODE0NTVkMDA4ZDU2MzZiNzU5ZWZjZjk2YjZi
+    YWE5NTE2OWVkZDY5M2JlMzhmZDZiMjQ1NTk4YzM0ZDc4MmQ0MWI=

data/README.md

@@ -12,6 +12,7 @@ It is designed around a number of core concepts like modularity, re-usability, t
 
 ### Installation
 
+#### environment variables
 First of all, make sure that the necessary environment variables are set on the BRPM instance, e.g. for a default BRPM installation:
 ```shell
 export BRPM_HOME=/opt/bmc/RLM
@@ -24,6 +25,7 @@ export PATH="$GEM_HOME/bin:$JRUBY_HOME/bin:$PATH"
 
 If BRPM is installed on a custom location you can modify the first line accordingly. The PATH variable is modified to make sure the ruby scripts that come with the modules are in the PATH.  
 
+#### .brpm
 Then create a file .brpm with the following contents in the root directory of the user account that runs BRPM:
 ```shell
 brpm_url: http://your-brpm-server:8088/brpm
@@ -32,6 +34,7 @@ brpm_api_token: ...
 
 Note that he brpm_api_token should be the token of a user that is defined in BRPM and that has administrative rights.
 
+#### framework
 Finally you can install the framework and the BRPM module (needed to configure the automation script wrappers of the modules) as following:
 ```shell
 gem install brpm_content_framework
@@ -50,8 +53,7 @@ Note that brpm_module_brpm is a module that contains a REST API client for BRPM
  
 Both gem files can be downloaded from the public gem repository rubygems.org. Just look up the name and on the gem's home page you will find a "Download" button that has a link to the latest version of the gem.
 
-### Usage
-
+#### modules
 OK now that the framework is installed the next thing to do is to install a couple of existing modules (or even build your own!). There is a list of available modules at the end of this page.
 
 A module can be installed as following:
@@ -66,6 +68,7 @@ brpm_install /path/to/module-name-x.x.x.gem
 
 The gem file of the module can be found on rubygems.org. 
 
+### Usage
 Once the module is installed you can immediately start using its contained automation scripts by linking the requests' steps to them.  
 
 ## Architecture
@@ -121,7 +124,7 @@ During the development life cycle, after you have committed the changes to your
 rake release
 ```
  
-By default the module will be published to the public rubygems.org repository. It is also possible however to publish your module to a [private repository](http://guides.rubygems.org/run-your-own-gem-server/) like [geminabox](https://github.com/geminabox/geminabox). See the [Demo] module (more specifically its Rakefile) for an example of this alternative. In this case you should not forget to add your private sem server as a source on the gem environment of the BRPM instance:
+By default the module will be published to the public rubygems.org repository. It is also possible however to publish your module to a [private repository](http://guides.rubygems.org/run-your-own-gem-server/) like [geminabox](https://github.com/geminabox/geminabox). See this [Rakefile](https://github.com/BMC-RLM/brpm_content_framework/blob/master/infrastructure/module_template/Rakefile_for_private_gem_repo) for an example of this alternative. In this case you should not forget to add your private sem server as a source on the gem environment of the BRPM instance:
 ```shell
 gem sources -a http://your-private-gem-server:9292/
 ```
@@ -327,8 +330,8 @@ For an example of how to update the status of the associated JIRA tickets after
 
 ## Publicly available modules:
 ### [BRPM](https://github.com/BMC-RLM/brpm_module_brpm)   
-### [BladeLogic](https://github.com/BMC-RLM/brpm_module_bladelogic)
+### [Bladelogic](https://github.com/BMC-RLM/brpm_module_bladelogic)
 ### [JIRA](https://github.com/BMC-RLM/brpm_module_jira)
 ### [Jenkins](https://github.com/BMC-RLM/brpm_module_jenkins)
-### [Demo](https://github.com/BMC-RLM/brpm_module_demo)
+### [Demo customer](https://github.com/BMC-RLM/brpm_module_demo)
 

data/config.yml

@@ -1,4 +1,4 @@
-version: 0.1.58
+version: 0.1.59
 
 author: Niek Bartholomeus
 email: niek.bartholomeus@gmail.com

data/module.gemspec

@@ -13,7 +13,7 @@ Gem::Specification.new do |spec|
   spec.summary       = config["summary"]
   spec.description   = config["description"]
 
-  spec.required_rubygems_version = "2.1.9"
+  spec.required_rubygems_version = ">= 2.1.9"
 
   spec.add_runtime_dependency "rest-client"
   spec.add_runtime_dependency "json"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: brpm_content_framework
 version: !ruby/object:Gem::Version
-  version: 0.1.58
+  version: 0.1.59
 platform: ruby
 authors:
 - Niek Bartholomeus
@@ -207,7 +207,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: 2.1.9
 requirements: []