-
Notifications
You must be signed in to change notification settings - Fork 13
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
Attributes are not added to node if it already exists but has no attributes #18
Comments
I believe this is caused by
|
I will try and review this in the next week. |
Per #18 adding check to see if existing node has no attributes but definition does. This was a case that the last round of revisions caused to be missed.
@rpolley You were spot on. Adding a check for the case where the definition has attributes defined but the existing element doesn't have any. Tested it on my end and it appears to work, but go ahead and pull from the development branch and give if a go before I package it up. |
@rpolley Bump |
@Areson - can you merge this in? i don't think we need to wait on rpolley as long as you tested it and it works. I've been waiting for this fix as well. |
@Areson seconding this, @1WindowsPuppetAdmin is probably in a better position than I am to validate that this works anyway. |
I've released the updated version on the forge. Thanks for your patience. |
I was trying to use this to edit some xml based config files, but I ran into an issue: consider the following xml file
somefile.xml
And the following manifest
Will result in an unchanged somefile.xml, however if the somefile.xml file was instead:
You would instead end up with
This is of course a simplified example, but it causes bugs when you try to use this to edit IIS config files, which use the convention of having attributes represent leaf settings that can be assigned values and the absence of a given attribute means that the setting the attribute represents takes its default value.
The text was updated successfully, but these errors were encountered: