sous-chefs / unbound Goto Github PK

I'd like to make sure we can still release this cookbook if we need to add a new maintainer. Could someone work to show me how to do a release?

🗣️ 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

Checks are not passing.

🥞 Cookbook version

Version of the cookbook where you are encountering the issue.

👩‍🍳 Chef-Infra Version

Version of chef-client in your environment.

🎩 Platform details

Operating system distribution and release version. Cloud provider if running in the cloud.

Steps To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

🚓 Expected behavior

All checks should be passing including integration tests.

➕ Additional context

Add any other context about the problem here. e.g. related issues or existing pull requests.

🗣️ 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.

The original cookbook had zone record management on the roadmap. Is this something we want to support?

🗣️ 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.

🗣️ 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.

🗣️ 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

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.

It looks like the forwarders template takes the literal value of the arrays without properly parsing it, causing the config to be invalid and fail.

I'm trying to pass an array of ips for an individual domain, which it looks like no longer works with v 1.0.0 of this cookbook.

# output of trying to start unbound with the example.
 service unbound reload
 * Reloading recursive DNS server unbound                                       No process in pidfile '/var/run/unbound.pid' found running; none killed.
                                                                         [fail]
root@dokken:/# service unbound restart
 * Restarting recursive DNS server unbound                                      /etc/unbound/unbound.conf.d/forward-zone.conf:21: error: unknown keyword '10.1.1.202'
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: stray '"'
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: unknown keyword ','
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: stray '"'
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: unknown keyword '10.1.1.203'
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: stray '"'
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: unknown keyword ']'
/etc/unbound/unbound.conf.d/forward-zone.conf:21: error: stray '"'
read /etc/unbound/unbound.conf failed: 8 errors in configuration file

#config on the machine
/etc/unbound/unbound.conf.d# cat forward-zone.conf
# Generated by Chef for dokken
#
# Forward zones
# Create entries like below, to make all queries for 'example.com' and
# 'example.org' go to the given list of servers. These servers have to handle
# recursion to other nameservers. List zero or more nameservers by hostname
# or by ipaddress. Use an entry with name "." to forward all queries.
# forward-zone:
#   name: "example.com"
#   forward-addr: 192.0.2.68
#   forward-addr: 192.0.2.73@5355  # forward to port 5355.
# forward-zone:
#   name: "example.org"
#   forward-host: fwd.example.com
server:
  forward-zone:
    name: "forward.example.com."
    forward-addr: "10.1.1.201"
  forward-zone:
    name: "forward2.example.com."
    forward-host: "["10.1.1.202", "10.1.1.203"]"
  forward-zone:
    name: "forward3.example.com."
    forward-host: "ns1.none"

# chef code
unbound_configure 'config' do
  local_zone 'id' => 'int_dummy_domain',
             'ns' => [{ 'dummy.com' => '127.0.0.1' }],
             'host' => [{ 'dummy.com' => '10.1.1.200' }]

#  forward_zone forwarder_zones
forward_zone 'forward1' => [{ 'forward.example.com' => '10.1.1.201' }],
              'forward2' => [{ 'forward2.example.com' => ['10.1.1.202', '10.1.1.203'] }],
              'forward3' => [{ 'forward3.example.com' => 'ns1.none' }]
  num_threads 2
  enable_ipv4 true
  enable_ipv6 true
  enable_tcp true
  enable_udp true
  access_control '127.0.0.1/8' => 'allow',
                 '0.0.0.0/0' => 'refuse'
  use_syslog 'yes'
  stats_interval 1
  stats_cumulative 'yes'
  stats_extended 'yes'
end

CoC, README headers, CONTRIBUTING, etc.

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

Refactor the cookbook to get things in a state that allows for future changes in Unbound. This will improve maintenance effort in the long-term.

This will cause breaking changes. Those changes will be documented to the best of abilities.

Determine future platform support. Most notably, the cookbook current supports FreeBSD along with Debian and Red Hat based distros. Is it still feasible to support all of these?