Scenario:

Verify GPG signatures easily as per this guide

Expected Result:

I can pass in a signature to gpg_verify and it is verified for me.

Cookbook version

0.3.0

Steps to Reproduce:

knife cookbook site download gpg
tree pgp

Expected Result:

tree pgp

├── Berksfile
├── CHANGELOG.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── TESTING.md
├── chefignore
├── libraries
│   └── helpers.rb
├── metadata.rb
├── resources
│   ├── install.rb
│   └── key.rb
├── spec
│   ├── spec_helper.rb
│   └── unit
│       ├── libraries
│       │   └── helpers_spec.rb
│       └── recipes
│           └── default_spec.rb
└── test
    ├── fixtures
    │   └── cookbooks
    │       └── test
    │           ├── metadata.rb
    │           └── recipes
    │               ├── default.rb
    │               └── dummy_key.rb
    └── integration
        └── default
            └── inspec
                └── default.rb

Actual Result:

├── CHANGELOG.md
├── CONTRIBUTING.md
├── README.md
├── attributes
│   └── default.rb
├── metadata.json
└── recipes
    └── default.rb

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

If the only thing in the .rubocop/yml is Dangerfile
Run the latest cookstyle
Remove .rubpopo.yml

Issue sprouted from sous-chefs/meta/issues/108. If not applicable then issue should be closed.

Cookbook version

master

Platform Details

Ubuntu 18.04

Scenario:

Do anything in batch mode with --no-tty on Ubuntu. GPG still asks for a password.

This looks like the tracking issue (or something similar on debian.org

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735241

Expected Result:

[What are you expecting to happen as the consequence of above reproduction steps?]

Actual Result:

[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]

There are several PRs that have been merged since the last release was made. Is the cookbook ready for a new release?

I am running on bionic so #12 is relatively important for me.

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

As part of our build process we should build each possible operating system separately

1. Ensure you have dokken setup and working:
2. dokken: aliased to KITCHEN_LOCAL_YAML=kitchen.dokken.yml kitchen
3. run dokken list, you should see a list of builds with dokken as the provider
4. download: https://github.com/sous-chefs/repo-management/blob/master/scripts/circleci_maker.rb and make this executable
5. run: dokken list -j | ./circleci_maker.rb > .circleci/config.yml

Issue sprouted from sous-chefs/meta/issues/112. If not applicable then issue should be closed.

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

Chef have released updated cookstyle rules, we should therefore run the auto fix against the cookbook

1. Ensure you are on the latest stable chef-workstation
2. Run cookstyle -a

Issue sprouted from sous-chefs/meta/issues/111. If not applicable then issue should be closed.

I noticed that the 0.3.0 version that's published in supermarket is an earlier version than what is in the master branch, which is still indicated as version '0.3.0' in the metadata. Unfortunately, I was looking forward to pulling the features in the master branch after seeing updates when I set 0.3.0 as a dependency in my cookbook. Since HEAD in the master branch has been merged, should the version be bumped and tagged as a newer release?

For now, I'm setting a commit version in Berksfile to pull the version I need.

cookbook 'gpg', git: 'https://github.com/sous-chefs/gpg', ref: '2f682a1'

🍑 Problem Statement

It is not currently possible to add keys to GPG via the --recv-keys option.

❔ Possible Solution

• Add a :receive_keys action & property to gpg_key
• GPG command needs to optionally accept --keyserver (or have a default to gnupgkeys.net)

⤴️ Describe alternatives you've considered

• Not doing it
• Continue shelling out e.g.

  execute 'Adding gpg key' do
   command "`which gpg2 || which gpg` --keyserver #{key_server} --homedir #{home_dir} --recv-keys #{new_resource.gpg_key}"
   only_if 'which gpg2 || which gpg'
 end

➕ Additional context

• RVM #414

Not sure if I'm missing something here, but how can I supply the passphrase?

The only action that currently executes as the resource user/group is generate. All other commands, such as import, execute as the chef-client user.

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

Update all CHANGELOGs to follow standard defined at https://keepachangelog.com/

Issue sprouted from sous-chefs/meta/issues/101. If not applicable then issue should be closed.

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

On the repo, ensure that Dangerfile matches https://github.com/sous-chefs/repo-management/blob/master/Dangerfile

Issue sprouted from sous-chefs/meta/issues/110. If not applicable then issue should be closed.