On Thu, Apr 9, 2009 at 9:58 AM, David Lutterkort <lut...@redhat.com> wrote: > > On Thu, 2009-04-09 at 08:25 +1000, Karl Bowden wrote: >> After a little testing, the problem is occuring directly in >> libruby-augeas. I get the same save file errors when trying to save a >> file after making changes and using quotes inside quotes. But the >> issue does not happen in augtool, but that may just be the way i'm >> using augtool. > > My very strong suspicion is that you are running into a similar problem > with quoting that Avi reported in ticket #2141, and that what happens is > that the changes string gets split incorrectly, so that what is sent to > ruby-augeas are actually malformed commands. > >> I am sure it has something to do with the way I am using the index >> searech ([.='/path']), but I am still working up an example to >> demonstrate with. > > That would be excellent, since frankly, I am getting a little lost in > this thread ... >
That's ok, turns out I was wrong again! Oh, and my problem is not the ticket #2141. Although it would be nice to get that behaviour reverted I have already worked around it by escape quoting all paths I use. I've only been learning enough ruby for two days just to test the augeas bindings, so mind the quality. Attached is a bindings demo that shows how the bindings handle quotes, and the output is below: libruby-augeas test sample root = /files/etc/exports rm /dir[1] : 3 set /dir[1] /home/server : true : /home/server set /dir[1]/client *.example.com : true : *.example.com set /dir[1]/client/option rw : true : rw save : true set /dir[1] '/home/server' : true : '/home/server' set /dir[1]/client '*.example.com' : true : '*.example.com' set /dir[1]/client/option 'rw' : true : 'rw' save : false Puppet does the right thing by sending the values to the augeas binding as they are given to puppet. And the augeas binding although not nessecaraly wrong, differs from how augtool handles the same example: ~/ augtool -r /tmp augtool> print /files/etc/exports augtool> set /files/etc/exports/dir[1] /home/server augtool> set /files/etc/exports/dir[1]/client *.example.com augtool> set /files/etc/exports/dir[1]/client/option rw augtool> print /files/etc/exports/ /files/etc/exports /files/etc/exports/dir = "/home/server" /files/etc/exports/dir/client = "*.example.com" /files/etc/exports/dir/client/option = "rw" augtool> set /files/etc/exports/dir[1] '/home/server' augtool> set /files/etc/exports/dir[1]/client '*.example.com' augtool> set /files/etc/exports/dir[1]/client/option 'rw' augtool> print /files/etc/exports/ /files/etc/exports /files/etc/exports/dir = "/home/server" /files/etc/exports/dir/client = "*.example.com" /files/etc/exports/dir/client/option = "rw" augtool> save Saved 1 file(s) augtool> Hopefully that will make it clearer what I am talking about. This does not appear to be a problem with puppet, but something people will have to be aware of if using puppet+augeas. - Karl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
augeas_test.rb
Description: application/ruby
