cool_stuff 0.0.2 → 0.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  !binary "U0hBMQ==":
3
3
  metadata.gz: !binary |-
4
- NjNiNTg3ZGM3ZjRmYzgzYjlkYzU3ZWU0ZDg1NmZlZDgyOTAyMDBhMQ==
4
+ NzgxMjE2YWM0MThmOTJlNmI4Y2Y0YjgzYTBlMDg5MzdlYzJiZGFiNw==
5
5
  data.tar.gz: !binary |-
6
- ZGRlMjI0NDlmZThlYzUxMThlYjY0N2U0MWQ5MzViMzA2NTg3MTg4NQ==
6
+ YzA2N2UzMTkyNmM1YTNmM2JhM2M1Y2M4ZjUzYTNmODgyMjM2MWM0NA==
7
7
  SHA512:
8
8
  metadata.gz: !binary |-
9
- NTY4ZDNhNWU0OGRlMGQyZDUwZTNmZjRjMGE0NTEwYzI0YWVmNjk3ZTkxNTU3
10
- N2E4ZGQxNWNiYTAyNmM4OWI0ZGU2Mzg3MTYxOGMyYmZkNWUyODAxYzQ4ZDJk
11
- NjI0Mjc5MzJjMmNhNWMwNjZmNTc5MzZhM2Y2YTcwMjJlM2UwNGI=
9
+ NDcyZTg1YWUyYWYxMzQxYTljNTFjZjYxNTNjNjFjMTM4ZWU1ZDk1YThkODAx
10
+ M2QxZmM5MjhmMjBmMjYxOWIyNzEyOWVkNjhjNTZhMTA3ODFjZjhhYjllMDVh
11
+ ODFkMDk3MGMzNTRlYTlmNzk1NDBjMGJiMGE4MWMzNmFkZWY4Njk=
12
12
  data.tar.gz: !binary |-
13
- M2JjMzk3ZmQwODJjZmRjMzAyZDdkOWE3NjBjZTg3Zjc0MTNlZjAyMzYyZjNi
14
- YjRiYTVkYTk3MWUxNTg5ZWYzNjhmODMxNjRiYzJjOTAyOGY3YzFkM2NjYjJh
15
- OThkNjQyM2QyYWE4ODMzOWNhYjE3MDIxOGI4YjA2NTFmZTc2MzU=
13
+ MzdhZWJjZWY3YTFmNmJlMjNhNDg2OTg5NDBkMmU4ZDM5MDhjNWE5Y2VhYjk1
14
+ ZDA5YTM1ZjJkNjg0ZWI5ZDEyZTQ4YjY0Y2MzNDQwMTU3NTFiYTVmNmZhOWFh
15
+ NDJmYzI4Njg2YzkxNzNiMTkxM2VmYzg4Zjg1NjdhNjNmODY0NTY=
@@ -0,0 +1,21 @@
1
+ # list all input and output params
2
+ params:
3
+ password:
4
+ name: Password
5
+ type: out-text
6
+
7
+ #friendly_name: <script friendly name> # this value will be used as the name of the automation script BRPM, if not specified the file name of the file will be used
8
+ description: Gets the password of the BRPM database
9
+
10
+ # if your automation script depends on an integration server, you can specify here the type of the integration server it needs
11
+ # during the installation the applicable integration server of the BRPM instance will then be linked to the automation script
12
+
13
+ # supported integration server types:
14
+ # Jira
15
+ # Hudson/Jenkins, Jenkins
16
+ # Remedy via AO, AO, "AtriumOrchestrator
17
+ # BMC Application Automation, Bladelogic
18
+ # RLM Deployment Engine, BRPD
19
+
20
+ #integration_server_type: <integration server type>
21
+
@@ -0,0 +1,13 @@
1
+ require 'yaml'
2
+
3
+ database_files = Dir["#{ENV["BRPM_HOME"]}/**/4.6.00.05/**/database.yml"]
4
+
5
+ if database_files.size > 0
6
+ database_yml = YAML.load_file(database_files.first)
7
+ password = database_yml["production"]["password"]
8
+ else
9
+ password = "No access to the password :-("
10
+ end
11
+
12
+
13
+ BrpmAuto.pack_response "password", password
data/config.yml CHANGED
@@ -2,7 +2,7 @@
2
2
  dependencies:
3
3
  - brpm_module_brpm # { version: x.x.x } # version is optional
4
4
 
5
- version: 0.0.2
5
+ version: 0.0.3
6
6
 
7
7
  friendly_name: Cool stuff # this value will be used to create an automation category in BRPM for the module, if not specified the name of the repository (minus "brpm_module_") will be used
8
8
  author: Niek Bartholomeus
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: cool_stuff
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.2
4
+ version: 0.0.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Niek Bartholomeus
@@ -79,6 +79,8 @@ files:
79
79
  - Rakefile
80
80
  - automations/addition.meta
81
81
  - automations/addition.rb
82
+ - automations/get_database_password.meta
83
+ - automations/get_database_password.rb
82
84
  - automations/get_environments.meta
83
85
  - automations/get_environments.rb
84
86
  - config.yml