Yes, that part I'm aware of. But the cloning of channels in our environment
uses the spacewalk-clone-by-date command. The API call will allow this to
continue and have the key set after the fact.

-Mathew

"When you do things right, people won't be sure you've done anything at
all." - God; Futurama

"We'll get along much better once you accept that you're wrong and neither
am I." - Me


On Thu, Feb 6, 2014 at 1:44 PM, Paul Robert Marino <prmari...@gmail.com>wrote:

> You can also do it via the web GUI in channel managment
>
>
>
> -- Sent from my HP Pre3
>
> ------------------------------
> On Feb 6, 2014 17:07, Mathew Snyder <mathew.sny...@gmail.com> wrote:
>
> Excellent! Good to see that.
>
> Related follow-up question:
> Is there documentation that better illustrates the creation and placement
> of a GPG key? I've read the section of the Satellite doc, but I'm left with
> questions that aren't answered there.
>
> -Mathew
>
> "When you do things right, people won't be sure you've done anything at
> all." - God; Futurama
>
> "We'll get along much better once you accept that you're wrong and
> neither am I." - Me
>
>
> On Thu, Feb 6, 2014 at 11:26 AM, Matthew Madey <mattma...@gmail.com>wrote:
>
>> The setDetails method should be the right API call to do what you want:
>>
>> client.channel.software.setDetails(SESSION_KEY, CHAN_ID, OPTION1,
>> OPTION2, etc, etc)
>>
>> Method: 
>> setDetails<http://www.spacewalkproject.org/documentation/api/2.0/handlers/ChannelSoftwareHandler.html#top>
>> Description:
>> Allows to modify channel attributes
>>
>> Parameters:
>>
>>    - string sessionKey
>>    - int channelDd - channel id
>>    - struct - channel_map
>>       - string "checksum_label" - new channel repository checksum label
>>       (optional)
>>       - string "name" - new channel name (optional)
>>       - string "summary" - new channel summary (optional)
>>       - string "description" - new channel description (optional)
>>       - string "maintainer_name" - new channel maintainer name (optional)
>>       - string "maintainer_email" - new channel email address (optional)
>>       - string "maintainer_phone" - new channel phone number (optional)
>>       - string "gpg_key_url" - new channel gpg key url (optional)
>>       - string "gpg_key_id" - new channel gpg key id (optional)
>>       - string "gpg_key_fp" - new channel gpg key fingerprint (optional)
>>
>> Returns:
>>
>>    - int - 1 on success, exception thrown otherwise.
>>
>>
>>
>> On Thu, Feb 6, 2014 at 2:20 PM, Mathew Snyder <mathew.sny...@gmail.com>wrote:
>>
>>> Is it possible to assign a gpg key to a clone channel that has been
>>> created using spacewalk-clone-by-date? The command itself has no capacity
>>> to assign one. Can it be done with the API after cloning?
>>>
>>> -Mathew
>>>
>>> "When you do things right, people won't be sure you've done anything at
>>> all." - God; Futurama
>>>
>>> "We'll get along much better once you accept that you're wrong and
>>> neither am I." - Me
>>>
>>> _______________________________________________
>>> Spacewalk-list mailing list
>>> Spacewalk-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to