You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspected node to be a problem because it could be some kind of magic word, but the following code is validated without any error (node is actually not a valid parameter for this type):
yeah, this seems to happen because of node being treated as a special keyword by puppet-lint. Actually, I'm seeing the same error with your second code example.
So a quick workaround would be to disable that check. (I'm afraid it's not possible to use inline comments to disable the check only for the code in question, since these comments don't prevent the syntax error from happening.)
Looking at Puppet's documentation for reserved wordsnode is listed there, but as far as I understand, it is allowed as a parameter name. (Parameter names doesn't seem to be counted as bare word strings.)
I don't see an easy way to make puppet-lint accept reserved words as parameter names. @rodjek could give you more insights on this.
Hi,
we use the module
crayfishx/db2
to setup db2 installation on our hosts. If we try to to use one particular type, puppet-lint fails withPuppet parser has no output:
The code
Line 63 is the
node => $db_node
partI suspected
node
to be a problem because it could be some kind of magic word, but the following code is validated without any error (node is actually not a valid parameter for this type):Does anyone have an idea why puppet-lint fails in this case?
The text was updated successfully, but these errors were encountered: