cocov_plugin_kit 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 40112f205669ad015d2fd5a49b1391820633eff66544fdd927d6e1cca210def1
-  data.tar.gz: 3a0a3faa3e564fe377d6595522aa7ae68e28bd312f54b7caa85c9d32cbb5fde1
+  metadata.gz: 1a8273e71e6a782ac8eb359fe94f8a4f36214122d738f462427dc0db7ac30d99
+  data.tar.gz: 4cb89031486138bd9893297792db58e92fe6099a4ffa43f067635683cf0c8f78
 SHA512:
-  metadata.gz: 034064d2eeb761d390912e9beb0f0f8acd09305663480e924e0a949f2bdf2aa9b437cc5a2c77323226fd15abd19f9753adc6301fc97f692718831bbff146c1ab
-  data.tar.gz: 328f90eaa0a1bc264d7270aaaf920c87c4b7b8cdc526694a1eb4bb5904aa5c47ed45d7f46d993cca82fa10daa0e4f12f9d2076dbebed6318354281431793f33d
+  metadata.gz: 3b59f4546faf3f18b6c45805352f6050f70b3c1cf0b8b436ce4bcbcef6e7fe2ec7a64c3f8c0faf8c0806d244d754ac286c835dac9938a4552153025835d688f9
+  data.tar.gz: 751d2360770a35d2e565142d12e502dd1932cc14c26357a305760e7ef95c6a4aae9c63d005f7657630225661014238c015907ae398ac760e0c2ff6ed7dd9440a

data/.rubocop.yml

@@ -31,3 +31,6 @@ Metrics/BlockLength:
 Lint/RescueException:
   Exclude:
     - lib/cocov/plugin_kit.rb
+
+Layout/FirstHashElementIndentation:
+  EnforcedStyle: consistent

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    cocov_plugin_kit (0.1.2)
+    cocov_plugin_kit (0.1.3)
 
 GEM
   remote: https://rubygems.org/

data/README.md

@@ -1,33 +1,69 @@
 # PluginKit
 
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/plugin_kit`. To experiment with that code, run `bin/console` for an interactive prompt.
-
-TODO: Delete this and the text above, and describe your gem
+PluginKit implements a utility library to help the development of Cocov Plugins using the Ruby programming language.
 
 ## Installation
 
-Install the gem and add to the application's Gemfile by executing:
+Cocov plugins should not contain Gemfiles. Instead, install the library directly
+using the `gem install` command, providing a specific version. For instance,
+
+```
+gem install cocov_plugin_kit -v 0.1.2
+```
 
-    $ bundle add plugin_kit
+## Usage
 
-If bundler is not being used to manage dependencies, install the gem by executing:
+### For simple plugins
 
-    $ gem install plugin_kit
+When implementing simple plugins, like for example, [brakeman](https://github.com/cocov-ci/brakeman/blob/master/plugin.rb),
+the block-based usage of PluginKit can be used:
 
-## Usage
+```ruby
+Cocov::PluginKit.run do
+  output = JSON.parse(exec(["my", "plugin", "--format", "json"], env: ENV))
+  # Process output...
+  emit_issue kind: # ...
+end
+```
+
+### For elaborate plugins
+
+For plugins requiring more organization or several internal methods, like [rubocop](https://github.com/cocov-ci/rubocop/blob/master/plugin.rb),
+`Cocov::PluginKit::Run` can be inherited into a new class, and `#run` can be
+overridden to be used as the plugin entrypoint, followed by a call to
+`Cocov::PluginKit.run`:
+
+```ruby
+class ElaboratePlugin < Cocov::PluginKit::Run
+  def run
+    output = JSON.parse(exec(["my", "plugin", "--format", "json"], env: ENV))
+    # Process output...
+    emit_issue kind: # ...
+  end
+end
 
-TODO: Write usage instructions here
+Cocov::PluginKit.run(ElaboratePlugin)
+```
 
 ## 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.
+A `docker-compose.yaml` is provided for allowing Ruby 2.6 to be used without
+requiring developers to install that version on their machines. When writing
+Dockerfiles, developers are advised to use the latest version available when
+building plugins.
 
-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).
+Use `docker compose run --rm -it ruby bash` to get a shell on the container;
+`bin/setup` can be used to install dependencies, `rspec` to run tests,
+`rubocop` to lint the codebase, and `bin/console` to get an interactive console
+that allows you to experiment.
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/plugin_kit. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/plugin_kit/blob/master/CODE_OF_CONDUCT.md).
+Bug reports and pull requests are welcome on GitHub at https://github.com/cocov-ci/plugin_kit.
+This project is intended to be a safe, welcoming space for collaboration, and
+contributors are expected to adhere to the [Cocov's code of conduct](https://github.com/cocov-ci/.github/blob/main/CODE_OF_CONDUCT.md).
 
 ## Code of Conduct
 
-Everyone interacting in the PluginKit project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/plugin_kit/blob/master/CODE_OF_CONDUCT.md).
+Everyone interacting in the Cocov project's codebases, issue trackers, chat rooms
+and mailing lists is expected to follow the [Cocov's code of conduct](https://github.com/cocov-ci/.github/blob/main/CODE_OF_CONDUCT.md).

data/lib/cocov/plugin_kit/realloc.rb

@@ -0,0 +1,34 @@
+# frozen_string_literal: true
+
+module Cocov
+  module PluginKit
+    # :nodoc:
+    class Realloc
+      def self.bindings
+        secrets_path = Pathname.new("/secrets")
+        bindings_path = secrets_path.join("bindings")
+        return {} if !bindings_path.exist? || bindings_path.directory?
+
+        bindings_path.read.split("\0").to_h do |entry|
+          from, to = entry.split("=", 2)
+          from_path = secrets_path.join(from)
+          to_path = Pathname.new(File.expand_path(to))
+          [from_path, to_path]
+        end
+      end
+
+      def self.mounts!
+        bindings.each do |from_path, to_path|
+          unless from_path.exist?
+            puts "Expected binding of #{from_path} to exist, but could not locate it"
+            exit 1
+          end
+
+          to_path.dirname.mkpath
+
+          FileUtils.cp from_path, to_path
+        end
+      end
+    end
+  end
+end

data/lib/cocov/plugin_kit/version.rb

@@ -2,6 +2,6 @@
 
 module Cocov
   module PluginKit
-    VERSION = "0.1.2"
+    VERSION = "0.1.3"
   end
 end

data/lib/cocov/plugin_kit.rb

@@ -8,8 +8,9 @@ require "tempfile"
 require "tmpdir"
 
 require_relative "plugin_kit/version"
-require_relative "plugin_kit/run"
 require_relative "plugin_kit/exec"
+require_relative "plugin_kit/realloc"
+require_relative "plugin_kit/run"
 
 module Cocov
   # PluginKit implements helpers for implementing Cocov Plugins in Ruby. The
@@ -29,6 +30,7 @@ module Cocov
       klass ||= Run
       instance = klass.new(output_file)
       Dir.chdir(instance.workdir) do
+        Realloc.mounts!
         if block_given?
           instance.instance_exec(&block)
         else

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cocov_plugin_kit
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Victor Gama
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-01-04 00:00:00.000000000 Z
+date: 2023-01-07 00:00:00.000000000 Z
 dependencies: []
 description: PluginKit implements helpers for running Cocov plugins
 email:
@@ -21,15 +21,16 @@ files:
 - ".editorconfig"
 - ".rspec"
 - ".rubocop.yml"
-- CODE_OF_CONDUCT.md
 - Gemfile
 - Gemfile.lock
 - LICENSE
 - README.md
 - Rakefile
+- cocov.output.bin
 - exe/cocov
 - lib/cocov/plugin_kit.rb
 - lib/cocov/plugin_kit/exec.rb
+- lib/cocov/plugin_kit/realloc.rb
 - lib/cocov/plugin_kit/run.rb
 - lib/cocov/plugin_kit/version.rb
 homepage: https://github.com/cocov-ci/plugin_kit

data/CODE_OF_CONDUCT.md

@@ -1,84 +0,0 @@
-# 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 hey@vito.io. 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.