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
[bind] missing state
fails zone/view configuration creation
#2432
Comments
No state is usually interpreted as "present" in DebOps roles, and the above logic doesn't really reflect that. But as far as I can remember, Anyway, I guess the logic above could be improved. A first thought would be to replace I think a better option might be to replace this:
With something like this:
|
I have used the suggested inventory which is in the documentation. Currently there is nothing in the production system but I'm testing everything in a virtual environment before I make this DebOps role available to my network. I liked your approach @Alphix, and I would like to try that in my own development environment. |
I am actually thinking different in this bug at this point. Since both variables are already filled with data, we should be checking only if it is NOT. So, why are we checking if it is |
In the current
master
branch of the documentation and themaster
branch of the code, BIND role documentation examples suggest to have views and zones withoutstate
attribute. However, this behavior is not acceptable because of the following code piece:debops/ansible/roles/bind/tasks/main.yml
Lines 85 to 102 in a4aa669
I don't see anything wrong with the code, but missing documentation can be improved in the future. This issue is created both for future references regarding "Make sure either zones or views are defined" error and possible documentation improvements in
debops.bind
role.The text was updated successfully, but these errors were encountered: