Hi Michael, On Mon, 2012-01-16 at 10:13 +0100, Michael Mraka wrote: > Parsons, Aron wrote: > % I was making use of configchannel_import in spacecmd at work last week > % and noticed that the API seems to eat newlines at the end of a file; ... > Hi, > > as for API call configchannel.createOrUpdatePath() - 'contents' can be > base64 encoded in which case it preserves both starting and ending > whitespaces. In this case you also have to set 'contents_enc64' to true.
Thanks, I tried this, and it can be used to work around the issue of eating whitespace/newlines at the end of the file. However, if I try to use it to work around the API blowing up on the ascii control character, the file seems to get uploaded to satellite OK, but theres then no way to download the content via the API (lookupFileInfo returns no contents, even though binary==false and the file can be viewed as text in the web UI) Can you advise any workaround for this? Is there any way to download files which contain characters which are not legal in XML via the API? Thanks, Steve _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
