add capability to disable systemd-resolved via role #86
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
renovate
waiting on upstream
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
CCCHH/ansible-infra!86
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add-systemd-resolved-config-role"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sometimes it is necessary to disable systemd-resolved on a host, for example when another DNS server is being configured. To make this easy, a new role is introduced (included by default via
base_configrole) which can do that. The defaults are not changed in any way so any host that is currently running with systemd-resolved will continue to do so.Looks good, just the one question/request and a README as the other roles have would also be nice. Especially since it might be a bit unintutive that the DNS settings also apply when the role disables systemd-resolved and since argument_specs are hardly human readable.
Two roles with nice READMEs as a reference:
@ -0,0 +1,11 @@# {{ ansible_managed }}Why overwrite this file instead of dropping our config into
/etc/resolved.conf.d?No specific reason. I just personally don't like to hide something in a
.ddirectory (which I find easy to overlook) when the intuitive efault would be to look in/etc/resolv.confwhen searching for settings.I guess for this use-case, where we don't want to enable additional functionality with minimal impact, but rather force this system to behave like we want to, overwriting
/etc/resolv.confis the reasonable choice.LGTM!