slosilo 2.2.2 → 3.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eee5855bf8948e460edebcc7e04399ad32ea9085f101860ddddb4687139a0bf8
-  data.tar.gz: 415fa1a618fbffda2ebf1dcb59abc42285d11d01afbc4697299708bbe3bd01fb
+  metadata.gz: 81d8f2c013b6f88d01bd7dd4c44b39c7cf0ffaa9385afca3e7ea826dae0855c8
+  data.tar.gz: acd627ef6ca45a404ce08c7bc680c8db7ea1ebdbe10d45b248ae09e59e804a02
 SHA512:
-  metadata.gz: '098214ef9bbb3ac810a28425e943fe81528573d54e7cdf85261c45cd1ab95fdc57a2387c629adc246339bc04488ff01a04d5655163bf8f423c2edacbb60f7a80'
-  data.tar.gz: 163a3a8097d4bafc592718d1bb37f1f2f8e25cbb5b637ba68c6478d787f131e08cc5d2a017f9d80bb5127c757d8f817b0a39c0e7c77557b45fc9e01206139305
+  metadata.gz: '098a049570888513d10bf23edacfb8c566f605a08a9e918a2a06c15839d406b14696edaf76c49b84820d3c0fc1147b0f7f754c74fdad680a98f919d134cabcc7'
+  data.tar.gz: 6cef96001fcc2932c23e106c732d9e7722afd2f6a8af11e99a023a49aa005bdc8ff9f3fa4ce278644b753acfe0e50953e14cf86114e78877368b95107a1126c0

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+# v3.0.0
+
+* Transition to Ruby 3. Consuming projects based on Ruby 2 shall use slosilo V2.X.X.
+
 # v2.2.2
 
 * Add rake task `slosilo:recalculate_fingerprints` which rehashes the fingerprints in the keystore.

data/Jenkinsfile

@@ -10,13 +10,22 @@ pipeline {
 
   stages {
     stage('Test') {
-      steps {
-        sh './test.sh'
+      parallel {
+        stage('Run tests on EE') {
+          agent { label 'executor-v2-rhel-ee' }
+          steps {
+            sh './test.sh'
+          }
+          post { always {
+            stash name: 'eeTestResults', includes: 'spec/reports/*.xml', allowEmpty:true
+          }}
+        }
 
-        junit 'spec/reports/*.xml'
-        cobertura coberturaReportFile: 'spec/coverage/coverage.xml'
-        sh 'cp spec/coverage/coverage.xml cobertura.xml'
-        ccCoverage("cobertura", "github.com/cyberark/slosilo")
+        stage('Run tests') {
+          steps {
+            sh './test.sh'
+          }
+        }
       }
     }
 
@@ -52,6 +61,14 @@ pipeline {
 
   post {
     always {
+      dir('ee-results'){
+        unstash 'eeTestResults'
+      }
+      junit 'spec/reports/*.xml, ee-results/spec/reports/*.xml'
+      cobertura coberturaReportFile: 'spec/coverage/coverage.xml'
+      sh 'cp spec/coverage/coverage.xml cobertura.xml'
+      ccCoverage("cobertura", "github.com/cyberark/slosilo")
+
       cleanupAndNotify(currentBuild.currentResult)
     }
   }

data/README.md

@@ -19,6 +19,9 @@ And then execute:
 
 ## Compatibility
 
+Version 3.0 introduced full transition to Ruby 3.
+Consumers who use slosilo in Ruby 2 projects, shall use slosilo V2.X.X.
+
 Version 2.0 introduced new symmetric encryption scheme using AES-256-GCM
 for authenticated encryption. It allows you to provide AAD on all symmetric
 encryption primitives. It's also **NOT COMPATIBLE** with CBC used in version <2.

data/lib/slosilo/attr_encrypted.rb

@@ -26,7 +26,10 @@ module Slosilo
         aad = options[:aad]
         # note nil.to_s is "", which is exactly the right thing
         auth_data = aad.respond_to?(:to_proc) ? aad.to_proc : proc{ |_| aad.to_s }
-        raise ":aad proc must take one argument" unless auth_data.arity.abs == 1 # take abs to allow *args arity, -1
+
+        # In ruby 3 .arity for #proc returns both 1 and 2, depends on internal #proc
+        # This method is also being called with aad which is string, in such case the arity is 1
+        raise ":aad proc must take two arguments" unless (auth_data.arity.abs == 2 || auth_data.arity.abs == 1)
 
         # push a module onto the inheritance hierarchy
         # this allows calling super in classes

data/lib/slosilo/version.rb

@@ -1,3 +1,3 @@
 module Slosilo
-  VERSION = "2.2.2"
+  VERSION = "3.0.0"
 end

data/slosilo.gemspec

@@ -22,7 +22,7 @@ Gem::Specification.new do |gem|
   gem.name          = "slosilo"
   gem.require_paths = ["lib"]
   gem.version       = Slosilo::VERSION
-  gem.required_ruby_version = '>= 1.9.3'
+  gem.required_ruby_version = '>= 3.0.0'
 
   gem.add_development_dependency 'rake'
   gem.add_development_dependency 'rspec', '~> 3.0'

data/spec/sequel_adapter_spec.rb

@@ -30,13 +30,13 @@ describe Slosilo::Adapters::SequelAdapter do
   describe "#put_key" do
     let(:id) { "id" }
     it "creates the key" do
-      expect(model).to receive(:create).with id: id, key: key.to_der
+      expect(model).to receive(:create).with(hash_including(:id => id, :key => key.to_der))
       allow(model).to receive_messages columns: [:id, :key]
       subject.put_key id, key
     end
 
     it "adds the fingerprint if feasible" do
-      expect(model).to receive(:create).with id: id, key: key.to_der, fingerprint: key.fingerprint
+      expect(model).to receive(:create).with(hash_including(:id => id, :key => key.to_der, :fingerprint => key.fingerprint))
       allow(model).to receive_messages columns: [:id, :key, :fingerprint]
       subject.put_key id, key
     end

data/test.sh

@@ -3,7 +3,7 @@
 iid=slosilo-test-$(date +%s)
 
 docker build -t $iid -f - . << EOF
-  FROM ruby
+  FROM ruby:3.0
   WORKDIR /app
   COPY Gemfile slosilo.gemspec ./
   RUN bundle

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: slosilo
 version: !ruby/object:Gem::Version
-  version: 2.2.2
+  version: 3.0.0
 platform: ruby
 authors:
 - Rafał Rzepecki
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-08-26 00:00:00.000000000 Z
+date: 2022-02-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -146,7 +146,6 @@ extra_rdoc_files: []
 files:
 - ".dockerignore"
 - ".github/CODEOWNERS"
-- ".github/PULL_REQUEST_TEMPLATE.md"
 - ".gitignore"
 - ".gitleaks.toml"
 - ".kateproject"
@@ -199,14 +198,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 1.9.3
+      version: 3.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
+rubygems_version: 3.1.6
 signing_key: 
 specification_version: 4
 summary: Store SSL keys in a database

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,21 +0,0 @@
-### What does this PR do?
-- _What's changed? Why were these changes made?_
-- _How should the reviewer approach this PR, especially if manual tests are required?_
-- _Are there relevant screenshots you can add to the PR description?_
-
-### What ticket does this PR close?
-Connected to #[relevant GitHub issues, eg 76]
-
-### Checklists
-
-#### Change log
-- [ ] The CHANGELOG has been updated, or
-- [ ] This PR does not include user-facing changes and doesn't require a CHANGELOG update
-
-#### Test coverage
-- [ ] This PR includes new unit and integration tests to go with the code changes, or
-- [ ] The changes in this PR do not require tests
-
-#### Documentation
-- [ ] Docs (e.g. `README`s) were updated in this PR, and/or there is a follow-on issue to update docs, or
-- [ ] This PR does not require updating any documentation