-
Notifications
You must be signed in to change notification settings - Fork 94
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
problem using colons in keys #64
Comments
I'll have to dig into reproducing this one a little more, but the stack trace seems to indicate that this is caused by the way the interpolation syntax is constructed (which makes it curious that this issue would come up on a string which is not supposed to be interpolated). Thanks for the report. |
OK, here's the most minimalist example I can still reproduce the error with. This is a node definition, say example.yml: parameters:
p: v
':':
bad: ${p} The error goes away when I replace HTH |
That does help, and seems to confirm the indication of the initial traceback that this issue exists along the interpolation code path. |
More digging around, I found that bluntly removing the call to Not entirely sure this doesn't break something else, but the test suite still works. |
Fix, class name references in 2nd level
I use a networking component for specifying default routes in ipv6, using the routing target as the key in yaml, as such:
If I do this on the highest level (node level) it's ok; but if it is done via class inclusion I get the following error. Given the double escape symbols I'm suspecting there is an issue with the use of ':' as part of the key.
The text was updated successfully, but these errors were encountered: