Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add zone management #2

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
Open

Add zone management #2

wants to merge 10 commits into from

Conversation

miska
Copy link

@miska miska commented Apr 9, 2019

Little cleanup and adding zone management.

miska and others added 6 commits April 9, 2019 20:23
Under normal circumstances, you don't need to specify user, as the
provided service file specifies the user.
The defaults copy the default behaviour. No need to explicitly specify
it.
This make passing just an user setting obsolete. There is much more to
be set.
Whenever zone file changes, knot should check the zone and reload it.
Important feature for knot.conf - allow arays without quites.
In pillar you specify
	address: '[ 192.168.1.1, 192.168.1.2]'
And in resulting knot.conf, you will end up with
	address: [ 192.168.1.1, 192.168.1.2]
If you use in pillar intuitive construction like this
	address: [ 192.168.1.1, 192.168.1.2]
The end result is invalid
	address: [ '192.168.1.1', '192.168.1.2']
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant