on_strum-healthcheck 0.1.0

data/.codeclimate.yml

@@ -0,0 +1,17 @@
+---
+
+checks:
+  argument-count:
+    enabled: false
+  method-complexity:
+    enabled: false
+
+plugins:
+  rubocop:
+    enabled: true
+    channel: rubocop-1-62
+    config:
+      file: .circleci/linter_configs/.rubocop.yml
+
+  reek:
+    enabled: true

data/.github/BRANCH_NAMING_CONVENTION.md

@@ -0,0 +1,36 @@
+# Branch naming convention
+
+## Branch naming
+
+> Please note for new pull requests create new branches from current `develop` branch only.
+
+Branch name should include type of your contribution and context. Please follow next pattern for naming your branches:
+
+```bash
+feature/add-some-feature
+technical/some-technical-improvements
+bugfix/fix-some-bug-name
+```
+
+## Before PR actions
+
+### Squash commits
+
+Please squash all branch commits into the one before opening your PR from your fork. It's simple to do with the git:
+
+```bash
+git rebase -i [hash your first commit of your branch]~1
+git rebase -i 6467fe36232401fa740af067cfd8ac9ec932fed2~1 # example
+```
+
+### Add commit description
+
+Please complete your commit description following next pattern:
+
+```code
+Technical/Add info files # should be the same name as your branch name
+
+* Added license, changelog, contributing, code of conduct docs
+* Added GitHub templates
+* Updated project license link
+```

data/.github/DEVELOPMENT_ENVIRONMENT_GUIDE.md

@@ -0,0 +1,26 @@
+# Development environment guide
+
+## Preparing
+
+Clone `ruby-on-strum-healthcheck` repository:
+
+```bash
+git clone https://github.com/on-strum/ruby-on-strum-healthcheck.git
+cd  ruby-gem
+```
+
+Configure latest Ruby environment:
+
+```bash
+echo 'ruby-3.2.0' > .ruby-version
+cp .circleci/gemspec_latest on_strum-healthcheck.gemspec
+```
+
+## Commiting
+
+Commit your changes excluding `.ruby-version`, `on_strum-healthcheck.gemspec`
+
+```bash
+git add . ':!.ruby-version' ':!on_strum-healthcheck.gemspec'
+git commit -m 'Your new awesome on_strum-healthcheck feature'
+```

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG] Your bug report title here"
+labels: bug
+assignees: Serhiy-Nazarov
+
+---
+
+<!-- Thanks for helping to make `on_strum-healthcheck` better! Before submit your bug, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->
+
+### New bug checklist
+
+- [ ] I have updated `on_strum-healthcheck` to the latest version
+- [ ] I have read the [Contribution Guidelines](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/CONTRIBUTING.md)
+- [ ] I have read the [documentation](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/README.md)
+- [ ] I have searched for [existing GitHub issues](https://github.com/on-strum/ruby-on-strum-healthcheck/issues)
+
+<!-- Please use next pattern for your bug report title: [BUG] Your bug report title here -->
+
+### Bug description
+<!-- Please include what's happening, expected behavior, and any relevant code samples -->
+
+##### Complete output when running `on_strum-healthcheck`, including the stack trace and command used
+
+<details>
+  <pre>[INSERT OUTPUT HERE]</pre>
+</details>

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: Suggest an idea
+title: "[FEATURE] Your feature request title here"
+labels: enhancement
+assignees: Serhiy-Nazarov
+
+---
+
+<!-- Thanks for helping to make `on_strum-healthcheck` better! Before submit your new feature request, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->
+
+### New feature request checklist
+
+- [ ] I have updated `on_strum-healthcheck` to the latest version
+- [ ] I have read the [Contribution Guidelines](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/CONTRIBUTING.md)
+- [ ] I have read the [documentation](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/README.md)
+- [ ] I have searched for [existing GitHub issues](https://github.com/on-strum/ruby-on-strum-healthcheck/issues)
+
+<!-- Please use next pattern for your feature request title: [FEATURE] Your feature request title here -->
+
+### Feature description
+
+<!-- Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+Describe the solution you'd like. A clear and concise description of what you want to happen.
+
+Describe alternatives you've considered. A clear and concise description of any alternative solutions or features you've considered. -->

data/.github/ISSUE_TEMPLATE/issue_report.md

@@ -0,0 +1,32 @@
+---
+name: Issue report
+about: Create a report to help us improve
+title: "[ISSUE] Your issue report title here"
+labels: ''
+assignees: Serhiy-Nazarov
+
+---
+
+<!-- Thanks for helping to make `on_strum-healthcheck` better! Before submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->
+
+### New issue checklist
+
+- [ ] I have updated `on_strum-healthcheck` to the latest version
+- [ ] I have read the [Contribution Guidelines](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/CONTRIBUTING.md)
+- [ ] I have read the [documentation](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/README.md)
+- [ ] I have searched for [existing GitHub issues](https://github.com/on-strum/ruby-on-strum-healthcheck/issues)
+
+<!-- Please use next pattern for your issue report title: [ISSUE] Your issue report title here -->
+
+### Issue description
+<!-- Please include what's happening, expected behavior, and any relevant code samples -->
+
+##### Complete output when running `on_strum-healthcheck`, including the stack trace and command used
+
+<details>
+
+```code
+  [INSERT OUTPUT HERE]
+```
+
+</details>

data/.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,22 @@
+---
+name: Question
+about: Ask your question to team
+title: "[QUESTION] Your question title here"
+labels: question
+assignees: Serhiy-Nazarov
+
+---
+
+<!-- Thanks for helping to make `on_strum-healthcheck` better! Before submit your question, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->
+
+### New question checklist
+
+- [ ] I have read the [Contribution Guidelines](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/CONTRIBUTING.md)
+- [ ] I have read the [documentation](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/README.md)
+- [ ] I have searched for [existing GitHub issues](https://github.com/on-strum/ruby-on-strum-healthcheck/issues)
+
+<!-- Please use next pattern for your question title: [QUESTION] Your question title here -->
+
+### Question
+
+<!-- Your question context here -->

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,49 @@
+# PR Details
+
+<!-- Provide a general summary of your changes in the Title above -->
+<!-- PR name should the same name as your branch name, example: -->
+<!-- Branch name is: feature/add-some-feature -->
+<!-- PR name should be: Feature/Add some feature -->
+
+## Description
+
+<!--- Describe your changes in detail -->
+
+## Related Issue
+
+<!--- This project only accepts pull requests related to open issues -->
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+<!--- Please link to the issue here: -->
+
+## Motivation and Context
+
+<!--- Why is this change required? What problem does it solve? -->
+
+## How Has This Been Tested
+
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Types of changes
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+
+- [ ] Docs change / refactoring / dependency upgrade
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## Checklist
+
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+
+- [ ] My code follows the code style of this project
+- [ ] My change requires a change to the documentation
+- [ ] I have updated the documentation accordingly
+- [ ] I have read the [**CONTRIBUTING** document](https://github.com/on-strum/ruby-on-strum-healthcheck/blob/master/CONTRIBUTING.md)
+- [ ] I have added tests to cover my changes
+- [ ] I have run `bundle exec rspec` from the root directory to see all new and existing tests pass
+- [ ] I have run `rubocop` and `reek` to ensure the code style is valid

data/.gitignore

@@ -0,0 +1,11 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+.rspec_status
+.DS_Store
+Gemfile.lock

data/.reek.yml

@@ -0,0 +1,39 @@
+---
+
+detectors:
+  IrresponsibleModule:
+    enabled: false
+
+  ControlParameter:
+    exclude:
+      - OnStrum::Healthcheck::Configuration#raise_unless
+      - OnStrum::Healthcheck::Configuration#validator_argument_type
+
+  LongParameterList:
+    exclude:
+      - OnStrum::Healthcheck::Configuration#raise_unless
+
+  ManualDispatch:
+    exclude:
+      - OnStrum::Healthcheck::Configuration#validator_services_callable
+
+  TooManyConstants:
+    exclude:
+      - OnStrum::Healthcheck::Configuration
+
+  TooManyStatements:
+    exclude:
+      - OnStrum::Healthcheck::Configuration#validate_attribute
+
+  UtilityFunction:
+    exclude:
+      - OnStrum::Healthcheck::Configuration#build_configuration_settings
+      - OnStrum::Healthcheck::Configuration#validator_argument_type
+      - OnStrum::Healthcheck::Configuration#validator_endpoint
+      - OnStrum::Healthcheck::Configuration#validator_http_status_failure
+      - OnStrum::Healthcheck::Configuration#validator_http_status_success
+      - OnStrum::Healthcheck::Configuration#validator_services_callable
+      - OnStrum::Healthcheck::Resolver#configuration
+
+exclude_paths:
+  - spec/support/helpers

data/.rspec

@@ -0,0 +1,2 @@
+--require spec_helper
+--format documentation

data/.ruby-gemset

@@ -0,0 +1 @@
+on_strum-healthcheck

data/.ruby-version

@@ -0,0 +1 @@
+ruby-2.5.0

data/CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2024-03-26
+
+### Added
+
+- First release of `on_strum-healthcheck`.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention
+  or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in
+  a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <admin@on-strum.org>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to `on_strum-healthcheck`
+
+Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+
+## Using the issue tracker
+
+The issue tracker is the preferred channel for [issue/bug reports](#issuebug-reports), [feature requests](#feature-requests), [questions](#questions) and submitting [pull requests](#pull-requests).
+
+## Issue/bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository. Good bug reports are extremely helpful - thank you!
+
+Guidelines for issue/bug reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been reported
+2. **Check if the issue has been fixed** — try to reproduce it using the latest `master` or `develop` branch in the repository
+3. `on_strum-healthcheck` [issue template](.github/ISSUE_TEMPLATE/issue_report.md)/[bug template](.github/ISSUE_TEMPLATE/bug_report.md)
+
+A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
+
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to _you_ to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
+
+## Questions
+
+We're always open to a new conversations. So if you have any questions just ask us.
+
+## Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
+
+**Please ask first** before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
+
+Please adhere to the coding conventions used throughout a project (indentation, accurate comments, etc.) and any other requirements (such as test coverage). Not all features proposed will be added but we are open to having a conversation about a feature you are championing.
+
+Guidelines for pull requests:
+
+1. `on_strum-healthcheck` [pull request template](.github/PULL_REQUEST_TEMPLATE.md)
+2. Fork the repo, checkout to `develop` branch
+3. Run the tests. This is to make sure your starting point works
+4. Read our [branch naming convention](.github/BRANCH_NAMING_CONVENTION.md)
+5. Create a new branch
+6. Read our [setup development environment guide](.github/DEVELOPMENT_ENVIRONMENT_GUIDE.md)
+7. Make your changes. Please note that your PR should include tests for the new codebase!
+8. Push to your fork and submit a pull request to `develop` branch

data/Gemfile

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022-2024 onStrum and friends
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.