16 Dub
2015
16 Dub
'15
16:58
I'm generating my Knot's config from a Jinja2 template, and I'm having a
problem with one thing. For example, if I have a list of elements,
[e1,e2,e3,e4], and I want to generate a "groups" config for these based
on a condition, and I do:
groups {
mygroup {
{% for x in list %}
{% if condition %}
{{ x }},
{% endif %}
{% endfor %}
}
However, this results in a syntax error, because the last element ends
with a comma, and then there's a closing bracket.
I tried to insert the comma conditionally, by checking to see if it was
the last element, but this can also fail if the last element didn't
match the condition.
So I thought about this ugly hack:
groups {
mygroup {
{% for x in list %}
{% if condition %}
,{{ x }}
{% endif %}
{% endfor %}
}
Notice that I have the comma *before* each element. This results in an
opening brace, a comma, and then the other elements. My supposition is
that Knot's syntax parser is okay with this, because it just sees a null
first element. If I check this with knotc's "checkconf", it says the
syntax is okay.
Can I safely use such a config?
Regards,
Anand
16 Dub
16 Dub
19:50
I'm generating my Knot's config from a Jinja2
template, and I'm having a
problem with one thing. For example, if I have a list of elements,
[e1,e2,e3,e4], and I want to generate a "groups" config for these based
on a condition
Quite off-topic for a DNS list, but have you considered using a Jinja2
`join' filter?
{{ [1, 2, 3] | join(',') }}
renders as
1, 2, 3
leaving off the last separator "," in this case.
-JP
20:19
On 16/04/15 19:50, Jan-Piet Mens wrote:
Quite off-topic for a DNS list, but have you
considered using a Jinja2
`join' filter?
Hi JP,
I do know about the 'join' filter, and use it in some of my templates
already. The issue here is Knot's requirement to name every interface
and remote. With what I need to do, I have to template all the remotes
first, and then remember the name of each remote, and then use that
later in the 'groups' section. My remotes list expands to one or more
addresses depending on various conditions (private addresses, IPv6
addresses, etc). A simple join won't help :(
Ideally, Knot would not have a 'groups' section, but rather, the remotes
section would allow grouping within it, much like BIND's 'masters' macro.
I'm following the development of Knot, and see that it's going to switch
to YAML for version 2. That should allow easier templating, especially
as Knot 2 is also introducing patterns, like NSD4.
Regards,
Anand
21:29
Hi Anand,
in JINJA2 template engine you have additiononal variables inside the loop.
See the http://jinja.pocoo.org/docs/dev/templates/ and the loop.last.
So your code could be like ...
{% for row in rows %}
{% if not loop.first %}
,
{% endif %}
{{ row }}
{% endfor %}
Peter
On 16/04/15 20:19, Anand Buddhdev wrote:
On 16/04/15 19:50, Jan-Piet Mens wrote:
--
*Peter Hudec*
Infraštruktúrny architekt
phudec(a)cnc.sk <mailto:phduec@cnc.sk>
*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2 35 000 100
Mobil:+421 905 997 203
*www.cnc.sk* <http:///www.cnc.sk>
Quite off-topic for a DNS list, but have you
considered using a Jinja2
`join' filter?
Hi JP,
I do know about the 'join' filter, and use it in some of my templates
already. The issue here is Knot's requirement to name every interface
and remote. With what I need to do, I have to template all the remotes
first, and then remember the name of each remote, and then use that
later in the 'groups' section. My remotes list expands to one or more
addresses depending on various conditions (private addresses, IPv6
addresses, etc). A simple join won't help :(
Ideally, Knot would not have a 'groups' section, but rather, the remotes
section would allow grouping within it, much like BIND's 'masters' macro.
I'm following the development of Knot, and see that it's going to switch
to YAML for version 2. That should allow easier templating, especially
as Knot 2 is also introducing patterns, like NSD4.
Regards,
Anand
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
21:32
Hi Anand,
in JINJA2 template engine you have additiononal variables inside the loop.
See the http://jinja.pocoo.org/docs/dev/templates/ and the loop.last.
So your code could be like ...
{% for row in rows %}
{% if not loop.first %}
,
{% endif %}
{{ row }}
{% endfor %}
Peter
On 16/04/15 20:19, Anand Buddhdev wrote:
On 16/04/15 19:50, Jan-Piet Mens wrote:
--
*Peter Hudec*
Infraštruktúrny architekt
phudec(a)cnc.sk <mailto:phduec@cnc.sk>
*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2 35 000 100
Mobil:+421 905 997 203
*www.cnc.sk* <http:///www.cnc.sk>
Quite off-topic for a DNS list, but have you
considered using a Jinja2
`join' filter?
Hi JP,
I do know about the 'join' filter, and use it in some of my templates
already. The issue here is Knot's requirement to name every interface
and remote. With what I need to do, I have to template all the remotes
first, and then remember the name of each remote, and then use that
later in the 'groups' section. My remotes list expands to one or more
addresses depending on various conditions (private addresses, IPv6
addresses, etc). A simple join won't help :(
Ideally, Knot would not have a 'groups' section, but rather, the remotes
section would allow grouping within it, much like BIND's 'masters' macro.
I'm following the development of Knot, and see that it's going to switch
to YAML for version 2. That should allow easier templating, especially
as Knot 2 is also introducing patterns, like NSD4.
Regards,
Anand
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
3305
days inactive
3305
days old
4 comments
4 participants
participants (4)
-
Anand Buddhdev -
Jan-Piet Mens -
Peter Hudec -
Peter Hudec