[Spacewalk-list] change to spacewalk-api to handle simple arrays

[Evan Frey]

I added the following to my /usr/bin/spacewalk-api


         if ($param =~ /^\[/) {
                 $param =~ s/[\[\]\"\']//g;
                 my @param = split(/,/, $param);
                 push @params, \@param;
         } else {
                 push @params, $param;
         }

to handle passing arrays.  So now commands like


spacewalk-api --server=127.0.0.1 --user=xxxxxx --pass=xxxxxx 
kickstart.profile.setChildChannels "%session%" CHANNELNAME 
"[CHILD1,CHILD2]"

will work.  It won't work with associative arrays like this, but that 
should be trivial to address.


On Thu, Jul 5, 2012 at 5:14 PM, Paul Robert Marino wrote:

> On Thu, Jul 5, 2012 at 3:48 PM, 
> <rhn-satellite at epperson.homelinux.net> wrote:
>> On Thu, July 5, 2012 15:29, fnwsa at yahoo.com wrote:
>>> Please ignore my previous message. Here is the updated one:
>>>
>>> Thank you for the info, Paul. It's very helpful. But one thing I 
>>> don't
>>> understand well, that is: RHEL 4 is in its Extended Life Phase and 
>>> Product
>>> Life Cycle that will be ended by February 28, 2015
>>> (https://access.redhat.com/support/policy/updates/errata/). Why do 
>>> you say
>>> "RHEL 4 and all of its derivatives are EOL (End of Life) don't 
>>> expect any
>>> thing to support it any more"? Would you please explain it further? 
>>> Thank
>>> you!
>>>
>>
>> If you have the paid extended support add-on, you can get _some_ 
>> security
>> errata for RHEL4 through 2/28/2015.  Otherwise, Paul is correct.
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> Essentially the extended life support is only intended for legacy
> systems which wouldn't be cost and or time effective to update because
> you plan on completely replacing them within the 3 year time frame any
> way.
> While you do still get critical security updates during the extended
> life phase you still would not pass a security audit without having an
> explicit plan including dates for when those systems were planed to be
> retired or replaced.
> No new software versions or addons should support RHEL 4 any more, and
> no one should be using RHEL 4, CentOS 4, or Scientific Linux 4 for new
> installs.
> If you have any thing running on RHEL 4 you should plan to replace,
> retire, or update to RHEL 6 it as soon as possible.
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list