status_check 0.1.1

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 ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: c5fae0e31034a83166c28383985871b7a80a8b5c
4
+ data.tar.gz: 1136aaf1178203c4424d50ed088c87c583b8d7cf
5
+ SHA512:
6
+ metadata.gz: e8c89609ac382f589813c909f4b331fafc506e06cc1f436144def2639a28d7823aaa5deb767679e52e7d7e99a91d217dae34f236074a860f17a4237118919b99
7
+ data.tar.gz: 62538db62476991699d8a977ab92c99cf7f600fcd5fed76fdd77a08af00941c5f203255126dbcc12dba9bd1323dc75d2483385f75dfbbbbaff934d70d406548d
data/.gitignore ADDED
@@ -0,0 +1,14 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /_yardoc/
4
+ /coverage/
5
+ /doc/
6
+ /pkg/
7
+ /spec/reports/
8
+ /tmp/
9
+ .idea/
10
+ .rspec
11
+
12
+ # rspec failure tracking
13
+ .rspec_status
14
+ .idea/workspace.xml
data/.travis.yml ADDED
@@ -0,0 +1,15 @@
1
+ sudo: false
2
+ language: ruby
3
+ rvm:
4
+ - 2.4.2
5
+ install:
6
+ - bin/setup
7
+ script:
8
+ - bundle exec rspec
9
+ - gem build status_check
10
+ deploy:
11
+ provider: rubygems
12
+ api_key: "$RUBY_GEMS_API_KEY"
13
+ on:
14
+ branch: master
15
+ tags: true
@@ -0,0 +1,74 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at vasilij@melnychuk.me. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
data/Gemfile ADDED
@@ -0,0 +1,6 @@
1
+ source "https://rubygems.org"
2
+
3
+ git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
4
+
5
+ # Specify your gem's dependencies in status_check.gemspec
6
+ gemspec
data/Gemfile.lock ADDED
@@ -0,0 +1,35 @@
1
+ PATH
2
+ remote: .
3
+ specs:
4
+ status_check (0.1.1)
5
+
6
+ GEM
7
+ remote: https://rubygems.org/
8
+ specs:
9
+ diff-lcs (1.3)
10
+ rake (10.5.0)
11
+ rspec (3.7.0)
12
+ rspec-core (~> 3.7.0)
13
+ rspec-expectations (~> 3.7.0)
14
+ rspec-mocks (~> 3.7.0)
15
+ rspec-core (3.7.1)
16
+ rspec-support (~> 3.7.0)
17
+ rspec-expectations (3.7.0)
18
+ diff-lcs (>= 1.2.0, < 2.0)
19
+ rspec-support (~> 3.7.0)
20
+ rspec-mocks (3.7.0)
21
+ diff-lcs (>= 1.2.0, < 2.0)
22
+ rspec-support (~> 3.7.0)
23
+ rspec-support (3.7.1)
24
+
25
+ PLATFORMS
26
+ ruby
27
+
28
+ DEPENDENCIES
29
+ bundler (~> 1.16)
30
+ rake (~> 10.0)
31
+ rspec (~> 3.0)
32
+ status_check!
33
+
34
+ BUNDLED WITH
35
+ 1.16.1
data/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2018 Matic Insurance
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
data/README.md ADDED
@@ -0,0 +1,118 @@
1
+ # StatusCheck
2
+
3
+ [![Build Status](https://travis-ci.org/matic-insurance/status_check.svg?branch=master)](https://travis-ci.org/matic-insurance/status_check)
4
+
5
+ Gem allows easy implementation of a status endpoint in your project.
6
+ It provides boilerplate code for commonly used components (Database, Redis, etc)
7
+ and allow usage of your custom status check.
8
+
9
+ As a result, the gem can produce hash with a status of every component or be embedded into the routes
10
+ for an automatic status endpoint.
11
+
12
+ ## Installation
13
+
14
+ Add this line to your application's Gemfile:
15
+
16
+ ```ruby
17
+ gem 'status_check'
18
+ ```
19
+
20
+ And then execute:
21
+
22
+ $ bundle
23
+
24
+ Or install it yourself as:
25
+
26
+ $ gem install status_check
27
+
28
+ ## Quick Usage
29
+
30
+ To use `status_check` you have to do 2 things:
31
+
32
+ First - create initializer, where you can define what services you want to be checked.
33
+ Example:
34
+ ```ruby
35
+ StatusCheck.configure do |c|
36
+ c.check(:my_service, service: StatusCheck::Services::BlockResult, connection: ->{ MyService.is_working? })
37
+ c.check(:database, service: StatusCheck::Services::ActiveRecordSql, connection: ->{ ActiveRecord::Base.connection })
38
+ c.check(:redis, service: StatusCheck::Services::ActiveRecordSql, connection: ->{ Redis.new(url: ENV['REDIS_URL']) })
39
+ end
40
+ ```
41
+
42
+ Second - define the route in your `routes.rb` file
43
+ ```ruby
44
+ Rails.application.routes.draw do
45
+ ...
46
+
47
+ match 'stats', to: StatusCheck::Router, via: :get
48
+
49
+ ...
50
+ end
51
+ ```
52
+
53
+ ## Custom usage
54
+
55
+ You can use status check without routing. In any place of application call:
56
+ ```ruby
57
+ success, report = StatusCheck.verify
58
+ puts success # true
59
+ puts report # [{service: 'database', success: true, status: 'OK'}, {service: 'redis', success: true, status: 'OK'}]
60
+ ```
61
+
62
+ Status check return tuple where first value is boolean (is all services checks are worked) and array of
63
+ (details for each service)
64
+
65
+ ## Builtin checks
66
+
67
+ #### ActiveRecordSql
68
+
69
+ Check connection to sql database configured via ActiveRecord
70
+
71
+ **class:** `StatusCheck::Services::ActiveRecordSql`
72
+ **connection:** block that returns instance of activerecord db connection. `->{ ActiveRecord::Base.connection }`
73
+ **verification:** verifies if applicaiton can read from database by executing `SELECT 1;`.
74
+
75
+ #### Redis
76
+
77
+ Checks connection to redis
78
+
79
+ **class:** `StatusCheck::Services::Redis`
80
+ **connection:** block that returns instance of redis. `->{ Redis.new(url: 'redis://redis.com') }`
81
+ **verification:** verifies if application can read from redis by executing `GET 1`.
82
+
83
+ #### BlockResult
84
+
85
+ Checks if connection block returns true or false
86
+
87
+ **class:** `StatusCheck::Services::BlockResult`
88
+ **connection:** block that returns true or false depending on status. `->{ MyService.is_working? }`
89
+ **verification:** verifies if block returns true or false.
90
+
91
+ ## Custom checks
92
+
93
+ There are two ways how you can implement your custom verifications.
94
+
95
+ - Implement custom service see `StatusCheck::Services::Abstract`
96
+ - Use BlockResult service and implement verification inside of connection block
97
+
98
+ ## Development
99
+
100
+ After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
101
+
102
+ To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
103
+
104
+ ## Contributing
105
+
106
+ Bug reports and pull requests are welcome on GitHub at https://github.com/matic-insurance/status_check. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
107
+
108
+ ## Code of Conduct
109
+
110
+ Everyone interacting in the StatusCheck project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/matic-insurance/status_check/blob/master/CODE_OF_CONDUCT.md).
111
+
112
+ ## License
113
+
114
+ [MIT](LICENSE)
115
+
116
+ ## Author Information
117
+
118
+ Made with love in Matic
data/Rakefile ADDED
@@ -0,0 +1,6 @@
1
+ require "bundler/gem_tasks"
2
+ require "rspec/core/rake_task"
3
+
4
+ RSpec::Core::RakeTask.new(:spec)
5
+
6
+ task :default => :spec
data/bin/console ADDED
@@ -0,0 +1,14 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require "bundler/setup"
4
+ require "status_check"
5
+
6
+ # You can add fixtures and/or initialization code here to make experimenting
7
+ # with your gem easier. You can also use a different console, if you like.
8
+
9
+ # (If you use this, don't forget to add pry to your Gemfile!)
10
+ # require "pry"
11
+ # Pry.start
12
+
13
+ require "irb"
14
+ IRB.start(__FILE__)
data/bin/setup ADDED
@@ -0,0 +1,8 @@
1
+ #!/usr/bin/env bash
2
+ set -euo pipefail
3
+ IFS=$'\n\t'
4
+ set -vx
5
+
6
+ bundle install
7
+
8
+ # Do any other automated setup that you need to do here
@@ -0,0 +1,30 @@
1
+ module StatusCheck
2
+ class Configuration
3
+ attr_accessor :checks
4
+
5
+ AVAILABLE_SERVICES = %I{postgresql redis}
6
+
7
+ def initialize
8
+ @checks = {}
9
+ end
10
+
11
+ def check(service_name, service:, connection:)
12
+ service = setup_service(service, connection)
13
+ validate_service(service)
14
+ @checks[service_name] = service
15
+ end
16
+
17
+ private
18
+ def setup_service(service_class, connection)
19
+ service_class.new(connection)
20
+ rescue => ex
21
+ raise Errors::NotValidParams, "Service #{service_class} cannot be instantiated with connection: #{ex.message}"
22
+ end
23
+
24
+ def validate_service(service)
25
+ unless service.respond_to?(:report_status)
26
+ raise Errors::NotValidParams, "Service #{service.class} should respond to report_status"
27
+ end
28
+ end
29
+ end
30
+ end
@@ -0,0 +1,6 @@
1
+ module StatusCheck
2
+ module Errors
3
+ class NotValidParams < StandardError; end
4
+ class MissingParams < StandardError; end
5
+ end
6
+ end
@@ -0,0 +1,11 @@
1
+ module StatusCheck
2
+ module Router
3
+ module_function
4
+
5
+ def call(hash)
6
+ result, report = ::StatusCheck.verify
7
+ status = result ? 200 : 503
8
+ [status, {}, [JSON.dump(report)]]
9
+ end
10
+ end
11
+ end
@@ -0,0 +1,33 @@
1
+ module StatusCheck
2
+ class Runner
3
+ attr_reader :checks
4
+
5
+ def initialize(checks)
6
+ @checks = checks
7
+ end
8
+
9
+ def verify
10
+ services_status = collect_services_status
11
+ report_status(services_status)
12
+ end
13
+
14
+ private
15
+ def report_status(services_status)
16
+ overall = services_status.all? { |service| service[:success] }
17
+ [overall, services_status]
18
+ end
19
+
20
+ def collect_services_status
21
+ checks.each_pair.map do |name, service|
22
+ verify_service(name, service)
23
+ end
24
+ end
25
+
26
+ def verify_service(name, service)
27
+ success, status = service.report_status
28
+ {service: name, success: success, status: status}
29
+ rescue => ex
30
+ {service: name, success: false, status: ex.to_s}
31
+ end
32
+ end
33
+ end
@@ -0,0 +1,34 @@
1
+ module StatusCheck
2
+ module Services
3
+ class Abstract
4
+ attr_reader :connection
5
+
6
+ def initialize(connection)
7
+ @connection = connection
8
+ end
9
+
10
+ def command
11
+ raise NotImplementedError, "Check command have to be defined"
12
+ end
13
+
14
+ def status_message(command_result, exception = nil)
15
+ return exception.to_s if !command_result && exception
16
+ return 'FAILED' if !command_result
17
+ 'OK'
18
+ end
19
+
20
+ def report_status
21
+ command_result = command
22
+ status_hash(command_result)
23
+ rescue StandardError => exception
24
+ status_hash(command_result, exception)
25
+ end
26
+
27
+ private
28
+
29
+ def status_hash(command_result, exception = nil)
30
+ [!!command_result, status_message(command_result, exception)]
31
+ end
32
+ end
33
+ end
34
+ end
@@ -0,0 +1,10 @@
1
+ module StatusCheck
2
+ module Services
3
+ class ActiveRecordSql < Abstract
4
+ def command
5
+ connection.call.execute("SELECT 1;")
6
+ true
7
+ end
8
+ end
9
+ end
10
+ end
@@ -0,0 +1,11 @@
1
+ require_relative 'abstract'
2
+
3
+ module StatusCheck
4
+ module Services
5
+ class BlockResult < Abstract
6
+ def command
7
+ !!connection.call
8
+ end
9
+ end
10
+ end
11
+ end
@@ -0,0 +1,10 @@
1
+ module StatusCheck
2
+ module Services
3
+ class Redis < Abstract
4
+ def command
5
+ connection.call.get("1")
6
+ true
7
+ end
8
+ end
9
+ end
10
+ end
@@ -0,0 +1,3 @@
1
+ module StatusCheck
2
+ VERSION = "0.1.1"
3
+ end
@@ -0,0 +1,25 @@
1
+ require "status_check/version"
2
+ require "status_check/errors"
3
+ Dir[File.dirname(__FILE__) + '/status_check/services/*.rb'].each { |file| require file }
4
+ require "status_check/configuration"
5
+ require "status_check/router"
6
+ require "status_check/runner"
7
+ require 'json'
8
+
9
+ module StatusCheck
10
+ class << self
11
+ attr_accessor :configuration
12
+ end
13
+
14
+ def self.configure
15
+ yield(configuration)
16
+ end
17
+
18
+ def self.configuration
19
+ @configuration ||= Configuration.new
20
+ end
21
+
22
+ def self.verify
23
+ Runner.new(configuration.checks).verify
24
+ end
25
+ end
@@ -0,0 +1,42 @@
1
+ lib = File.expand_path("../lib", __FILE__)
2
+ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
3
+ require "status_check/version"
4
+
5
+ Gem::Specification.new do |spec|
6
+ spec.name = "status_check"
7
+ spec.version = StatusCheck::VERSION
8
+ spec.authors = ["Vasyl Melnychuk", "Volodymyr Mykhailyk"]
9
+ spec.email = ["vasyl.m@matic.com"]
10
+ spec.licenses = ['MIT']
11
+
12
+ spec.summary = %q{Status endpoint code to verify components availability of your application}
13
+ spec.description = %q{
14
+ Gem allows easy implementation of a status endpoint in your project.
15
+ It provides boilerplate code for commonly used components (Database, Redis, etc)
16
+ and allow usage of your custom status check.
17
+
18
+ As a result, the gem can produce hash with a status of every component or be embedded into the routes
19
+ for an automatic status endpoint.
20
+ }
21
+ spec.homepage = "https://github.com/matic-insurance/status_check"
22
+
23
+ # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
24
+ # to allow pushing to a single host or delete this section to allow pushing to any host.
25
+ if spec.respond_to?(:metadata)
26
+ spec.metadata["allowed_push_host"] = "https://rubygems.org"
27
+ else
28
+ raise "RubyGems 2.0 or newer is required to protect against " \
29
+ "public gem pushes."
30
+ end
31
+
32
+ spec.files = `git ls-files -z`.split("\x0").reject do |f|
33
+ f.match(%r{^(test|spec|features)/})
34
+ end
35
+ spec.bindir = "exe"
36
+ spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
37
+ spec.require_paths = ["lib"]
38
+
39
+ spec.add_development_dependency "bundler", "~> 1.16"
40
+ spec.add_development_dependency "rake", "~> 10.0"
41
+ spec.add_development_dependency "rspec", "~> 3.0"
42
+ end
metadata ADDED
@@ -0,0 +1,114 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: status_check
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.1
5
+ platform: ruby
6
+ authors:
7
+ - Vasyl Melnychuk
8
+ - Volodymyr Mykhailyk
9
+ autorequire:
10
+ bindir: exe
11
+ cert_chain: []
12
+ date: 2018-06-01 00:00:00.000000000 Z
13
+ dependencies:
14
+ - !ruby/object:Gem::Dependency
15
+ name: bundler
16
+ requirement: !ruby/object:Gem::Requirement
17
+ requirements:
18
+ - - "~>"
19
+ - !ruby/object:Gem::Version
20
+ version: '1.16'
21
+ type: :development
22
+ prerelease: false
23
+ version_requirements: !ruby/object:Gem::Requirement
24
+ requirements:
25
+ - - "~>"
26
+ - !ruby/object:Gem::Version
27
+ version: '1.16'
28
+ - !ruby/object:Gem::Dependency
29
+ name: rake
30
+ requirement: !ruby/object:Gem::Requirement
31
+ requirements:
32
+ - - "~>"
33
+ - !ruby/object:Gem::Version
34
+ version: '10.0'
35
+ type: :development
36
+ prerelease: false
37
+ version_requirements: !ruby/object:Gem::Requirement
38
+ requirements:
39
+ - - "~>"
40
+ - !ruby/object:Gem::Version
41
+ version: '10.0'
42
+ - !ruby/object:Gem::Dependency
43
+ name: rspec
44
+ requirement: !ruby/object:Gem::Requirement
45
+ requirements:
46
+ - - "~>"
47
+ - !ruby/object:Gem::Version
48
+ version: '3.0'
49
+ type: :development
50
+ prerelease: false
51
+ version_requirements: !ruby/object:Gem::Requirement
52
+ requirements:
53
+ - - "~>"
54
+ - !ruby/object:Gem::Version
55
+ version: '3.0'
56
+ description: "\n Gem allows easy implementation of a status
57
+ endpoint in your project.\n It provides boilerplate code
58
+ for commonly used components (Database, Redis, etc)\n and
59
+ allow usage of your custom status check.\n\n As a result,
60
+ the gem can produce hash with a status of every component or be embedded into the
61
+ routes\n for an automatic status endpoint.\n "
62
+ email:
63
+ - vasyl.m@matic.com
64
+ executables: []
65
+ extensions: []
66
+ extra_rdoc_files: []
67
+ files:
68
+ - ".gitignore"
69
+ - ".travis.yml"
70
+ - CODE_OF_CONDUCT.md
71
+ - Gemfile
72
+ - Gemfile.lock
73
+ - LICENSE
74
+ - README.md
75
+ - Rakefile
76
+ - bin/console
77
+ - bin/setup
78
+ - lib/status_check.rb
79
+ - lib/status_check/configuration.rb
80
+ - lib/status_check/errors.rb
81
+ - lib/status_check/router.rb
82
+ - lib/status_check/runner.rb
83
+ - lib/status_check/services/abstract.rb
84
+ - lib/status_check/services/active_record_sql.rb
85
+ - lib/status_check/services/block_result.rb
86
+ - lib/status_check/services/redis.rb
87
+ - lib/status_check/version.rb
88
+ - status_check.gemspec
89
+ homepage: https://github.com/matic-insurance/status_check
90
+ licenses:
91
+ - MIT
92
+ metadata:
93
+ allowed_push_host: https://rubygems.org
94
+ post_install_message:
95
+ rdoc_options: []
96
+ require_paths:
97
+ - lib
98
+ required_ruby_version: !ruby/object:Gem::Requirement
99
+ requirements:
100
+ - - ">="
101
+ - !ruby/object:Gem::Version
102
+ version: '0'
103
+ required_rubygems_version: !ruby/object:Gem::Requirement
104
+ requirements:
105
+ - - ">="
106
+ - !ruby/object:Gem::Version
107
+ version: '0'
108
+ requirements: []
109
+ rubyforge_project:
110
+ rubygems_version: 2.6.13
111
+ signing_key:
112
+ specification_version: 4
113
+ summary: Status endpoint code to verify components availability of your application
114
+ test_files: []