Skip to content

Commit

Permalink
rspec pkcs12
Browse files Browse the repository at this point in the history
  • Loading branch information
marcusdots committed Jan 10, 2025
1 parent 07e2469 commit f8caa89
Showing 1 changed file with 6 additions and 5 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,18 @@
# in the meantime we won't use x509_certificate matcher
describe 'x509 to pkcs12 to pem key' do
it_behaves_like 'the example', 'x509_pkcs12_pemkey.pp' do
it { expect(file('/tmp/sample_x509.crt')).to be_file.and(have_attributes(owner: 'root')) }
# it { expect(x509_certificate('/tmp/foo.example.com.crt')).to be_certificate.and(have_attributes(subject: 'C = CH, O = Example.com, CN = foo.example.com')) }
it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) }

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 11 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.crt')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10
it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) }

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 12 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/sample_x509.key')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10
it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) }

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 13 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Failure/Error: it { expect(file('/tmp/export.pkcs12.p12')).to be_file.and(its(:size) { is_expected.to > 0 }) } `its` is not available from within an example (e.g. an `it` block) or from constructs that run in the scope of an example (e.g. `before`, `let`, etc). It is only available on an example group (e.g. a `describe` or `context` block). Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

describe x509_certificate('/tmp/sample_x509.crt') do
it { is_expected.to be_certificate }

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 16 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be certificate Failure/Error: it { is_expected.to be_certificate } expected `X509 certificate "/tmp/sample_x509.crt".certificate?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10
it { is_expected.to be_valid }

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 17 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" is expected to be valid Failure/Error: it { is_expected.to be_valid } expected `X509 certificate "/tmp/sample_x509.crt".valid?` to be truthy, got false Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10
# its(:subject) { is_expected.to match_without_whitespace(%r{C = CH, O = Example.com, CN = foo.example.com}) }
its(:keylength) { is_expected.to eq 1024 }

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 18 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example X509 certificate "/tmp/sample_x509.crt" keylength is expected to eq 1024 Failure/Error: its(:keylength) { is_expected.to eq 1024 } expected: 1024 got: 0 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10
end

# it { expect(file('/tmp/foo.example.com.key')).to be_file.and(have_attributes(owner: 'nobody', mode: '600')) }
# it { expect(x509_private_key('/tmp/foo.example.com.key', passin: 'pass:mahje1Qu')).to have_matching_certificate('/tmp/foo.example.com.crt') }
describe command('openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:') do
its(:exit_status) { is_expected.to eq 0 }

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 9

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - CentOS 9

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - AlmaLinux 8

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 12

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Debian 11

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Ubuntu 20.04

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - OracleLinux 8

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - Ubuntu 24.04

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 7 - Rocky 9

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10

Check failure on line 22 in spec/acceptance/x509_pkcs12_spec.rb

View workflow job for this annotation

GitHub Actions / Puppet / Puppet 8 - AlmaLinux 9

x509 to pkcs12 to pem key behaves like the example Command "openssl -text -noout -in /tmp/export.pkcs12.p12 -inpass pass:" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { is_expected.to eq 0 } expected: 0 got: 1 (compared using ==) Shared Example Group: "the example" called from ./spec/acceptance/x509_pkcs12_spec.rb:10
end
end
end

0 comments on commit f8caa89

Please sign in to comment.