base-jobs/roles/configure-unbound
Clark Boylan 080ecb4579 Set file modes explicitly
Ansible changed, then unchanged their behavior around file modes, but
being explicit is likely a good idea to handle any new future changes
from ansible.

We set modes generously (to 755 for dirs and 644 for files) to avoid
unexpected access problems. Note that depending on the perms in AFS this
may cause a perms ot update on existing dirs but that should be fine as
long as we aren't making them more restrictive.

Finally we skip two cases where modes are required by the linting rule
because they are tarball extraction steps and applying a single mode to
all dirs and files in a tarball doens't make a ton of sense.

Includes bumping linter configuration.

Change-Id: Iacf41549928ba7f05f0f71a79ddef1b6e1154e2a
Co-authored-by: Sorin Sbarnea <ssbarnea@redhat.com>
2020-08-28 18:49:53 +01:00
..
defaults Switch from 1.1.1.1 to 1.0.0.1 2019-04-25 13:20:12 +00:00
handlers Initial pass at global opendev base job set 2019-01-28 13:59:24 -08:00
tasks Set file modes explicitly 2020-08-28 18:49:53 +01:00
templates Initial pass at global opendev base job set 2019-01-28 13:59:24 -08:00
vars Initial pass at global opendev base job set 2019-01-28 13:59:24 -08:00
README.rst Switch from 1.1.1.1 to 1.0.0.1 2019-04-25 13:20:12 +00:00

README.rst

An ansible role to dynamically configure DNS forwarders for the unbound caching service. IPv6 will be preferred when there is a usable IPv6 default route, otherwise IPv4.

Note

This is not a standalone unbound configuration role. Base setup is done during image builds in project-config:nodepool/elements/nodepool-base/finalise.d/89-unbound; here we just do dynamic configuration of forwarders based on the interfaces available on the actual host.

Role Variables