mqtt_api_client 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: d9c75dac8a27f93fc8756bb64868aba970a57a5e99267e749820acda6009745f
+  data.tar.gz: 0ef832f1ca9e28be3226788205339ac92d228ee1ec013d2679d09096df63bfa7
+SHA512:
+  metadata.gz: e00b819611be0ddc22ed5d93e378b1ed4f7546d5b531ab0a57b5cca49b83ecd5832055017d27c214865e1513ef3939960558b964915c182357299d2400656044
+  data.tar.gz: 57d53b71b510c4455c0064fce28ac11386fe724f5c2f9435d0725d6a5f43fb186bb26e4912aeab7dd2d4b42638325892140f260c97446a3fb746c61c718b80e0

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,30 @@
+require:
+  - rubocop-rake
+  - rubocop-rspec
+
+AllCops:
+  TargetRubyVersion: 3.1
+  NewCops: enable
+
+Layout/LineLength:
+  Enabled: false
+
+Metrics/BlockLength:
+  Enabled: false
+
+Metrics/MethodLength:
+  Enabled: false
+
+RSpec/ExampleLength:
+  Enabled: false
+
+RSpec/MultipleExpectations:
+  Enabled: false
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2024-05-06
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at sumskyi@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2024 Vladyslav Sumskyi
+
+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.

data/README.md

@@ -0,0 +1,37 @@
+# MqttApiClient
+
+Ruby gem that enables sending commands to MQTT clients. The gem should support secure connections to the MQTT broker using SSL.
+
+## Installation
+
+TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
+
+Install the gem and add to the application's Gemfile by executing:
+
+    $ bundle add macklabsinc/mqtt_api_client
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+    $ gem install macklabsinc/mqtt_api_client
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Development
+
+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.
+
+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 the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/mqtt_api_client. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://bitbucket.com/macklabsinc/mqtt_api_client/blob/master/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the MqttApiClient project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://bitbucket.com/macklabsinc/mqtt_api_client/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/bitbucket-pipelines.yml

@@ -0,0 +1,19 @@
+#  Template Ruby build
+
+#  This template allows you to validate your Ruby code.
+#  The workflow allows running tests and code linting on the default branch.
+
+image: ruby:3.1.2
+
+pipelines:
+  default:
+    - parallel:
+      - step:
+          name: Test
+          script:
+            - bundle install
+            - bundle exec rspec && bundle exec rubocop
+      - step:
+          name: Lint code
+          script:
+            - ruby -wc **/*.rb

data/lib/mqtt_api_client/command.rb

@@ -0,0 +1,95 @@
+# frozen_string_literal: true
+
+require "logger"
+
+module MqttApiClient
+  # commands implemented
+  class Command
+    attr_reader :mqtt_client, :crt, :key, :host, :logger
+
+    #
+    # @param [File|String], crt
+    # @param [File|String], key
+    def initialize(crt, key, host)
+      @crt = if File.file? crt
+               File.read crt
+             else
+               crt
+             end
+      @key = if File.file? key
+               File.read key
+             else
+               key
+             end
+
+      @host = host
+
+      @logger = Logger.new("log/command.log", "daily")
+      @logger.info "Command logger initialized at #{Time.now}"
+
+      connect
+    end
+
+    # rubocop:disable Style/EmptyElse
+    def file_list(device_identifier)
+      subscribed_topic = "device/#{device_identifier}/file_list"
+
+      mqtt_client.subscribe(subscribed_topic)
+      mqtt_client.publish("device/#{device_identifier}/command", "file_list")
+
+      mqtt_client.get do |topic, message|
+        mqtt_client.unsubscribe(subscribed_topic) if topic == subscribed_topic
+
+        if topic == subscribed_topic
+          logger.info "New file_list: #{message}"
+
+          # do some logic with a message, probably update device file_list in the DB ?
+
+          return message
+        else
+          # I don't want to raise exception here because we are
+          # getting messages from the whole mqtt queue, one by one,
+          # and the next message could be that what we need
+        end
+      end
+    end
+
+    def health_status(device_identifier)
+      subscribed_topic = "device/#{device_identifier}/health_status"
+      mqtt_client.subscribe(subscribed_topic)
+
+      mqtt_client.publish("device/#{device_identifier}/command", "health_status")
+
+      mqtt_client.get do |topic, message|
+        mqtt_client.unsubscribe(subscribed_topic) if topic == subscribed_topic
+
+        if topic == subscribed_topic
+          logger.info "New health_status: #{message}"
+
+          # do some logic with a message, probably update device health_status in the DB ?
+
+          return message
+        else
+          # I don't want to raise exception here because we are
+          # getting messages from the whole mqtt queue, one by one,
+          # and the next message could be that what we need
+        end
+        # rubocop:enable Style/EmptyElse
+      end
+    end
+
+    private
+
+    def connect
+      @mqtt_client = MQTT::Client.new
+      @mqtt_client.host = host
+      @mqtt_client.port = 8883
+      @mqtt_client.ssl = true
+
+      @mqtt_client.cert = crt
+      @mqtt_client.key = key
+
+      @mqtt_client.connect
+    end
+  end
+end

data/lib/mqtt_api_client/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module MqttApiClient
+  VERSION = "0.1.0"
+end

data/lib/mqtt_api_client.rb

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require "amazing_print"
+require "mqtt"
+require_relative "mqtt_api_client/version"
+require_relative "mqtt_api_client/command"
+
+module MqttApiClient
+  class Error < StandardError; end
+end

data/sig/mqtt_api_client.rbs

@@ -0,0 +1,4 @@
+module MqttApiClient
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,74 @@
+--- !ruby/object:Gem::Specification
+name: mqtt_api_client
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Vladyslav Sumskyi
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2024-05-21 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: mqtt
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.6.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.6.0
+description: MQTT API Client
+email:
+- sumskyi@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".rspec"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- LICENSE.txt
+- README.md
+- Rakefile
+- bitbucket-pipelines.yml
+- lib/mqtt_api_client.rb
+- lib/mqtt_api_client/command.rb
+- lib/mqtt_api_client/version.rb
+- sig/mqtt_api_client.rbs
+homepage: https://bitbucket.org/macklabsinc/mqtt_api_client/src/master/
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+  homepage_uri: https://bitbucket.org/macklabsinc/mqtt_api_client/src/master/
+  source_code_uri: https://bitbucket.org/macklabsinc/mqtt_api_client/src/master/
+  changelog_uri: https://bitbucket.org/macklabsinc/mqtt_api_client/src/master/CHANGELOG.md
+  rubygems_mfa_required: 'false'
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 3.1.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.4.10
+signing_key: 
+specification_version: 4
+summary: MQTT API Client
+test_files: []