-
Notifications
You must be signed in to change notification settings - Fork 913
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
zone2sql failed when it reached an $include statement ending in ; #14382
Comments
Just for perspective, there is no need to have a However (The observed behavior also raises the question of whether the same kind of misparsing of comments can occur in other contexts as well, or if maybe a whole different parser is used for these special directives starting with |
sadly the existing system were looking to convert has many of these includes in this style and it writes the files back out often so even if we added a space or put quotes around the existing string it will get replaced not long after. ( this just added one more nail in the coffin of why its being replaced 😆 ) |
Fair enough. it might well be too much of a pain to improve the thing that generates those entries, especially if you are migrating away from that system anyway. But regarding adding spaces and whatnot, if there really is no actual comment text (like in your example), then it seems more straightforward to eliminate the |
Correct in my case theres no comment text. Its the last character on that line |
Short description
when converting a bind config we found failures to open files. it turns out it was attempting to open files with a semicolon at the end of the filename
Environment
Steps to reproduce
create some bind config files.
create a file that includes another file:
file1.conf
file2:
attempt to export:
Expected behaviour
file is parsed correctly and included
Actual behaviour
Other information
include seems to be handled correctly IF the include path has quotes around it:
$INCLUDE "reverse_zones/1/2/file2";
but is not handled correctly if there is no quotes.$INCLUDE reverse_zones/1/2/file2;
when there are no quotes it includes the semicolon from the end of the string
The text was updated successfully, but these errors were encountered: