[katello-devel] Notices generated from async tasks

Tomas Strachota tstrachota at redhat.com
Mon Jan 23 09:47:07 UTC 2012


On 01/20/2012 04:12 PM, Brad Buckingham wrote:
> On 01/20/2012 09:57 AM, Bryan Kearney wrote:
>> On 01/20/2012 09:51 AM, Brad Buckingham wrote:
>>> On 01/20/2012 08:28 AM, Bryan Kearney wrote:
>>>> On 01/20/2012 05:13 AM, Lukas Zapletal wrote:
>>>>> On Thu, Jan 19, 2012 at 11:28:15PM +0100, Tomas Strachota wrote:
>>>>>> 1) Determine whether a task was started from CLI or UI. Notices
>>>>>> would be generated only for the UI ones. Disadvantage here is that
>>>>>> if I start a task from CLI and switch to UI while it's still
>>>>>> running, I won't see the result notice.
>>>>>
>>>>> This is really not an issue, if you started it in the CLI, you should
>>>>> not see it in the UI. Period.
>>>>>
>>> [brad] I think there is actually a bigger question here. It is bigger
>>> than this single instance of a notice on an async promotion task. Today,
>>> for the UI, we have the notifications which store information about
>>> various actions that an admin performs via the UI. This gives the admin
>>> a bit of 'history' and perhaps could be used to support things like
>>> auditing in the future (if needed). Do we have anything like that for
>>> the CLI? Should we? Would an admin ever care to see what actions were
>>> performed from the CLI? If not, then I'm not sure having them for the UI
>>> actions is of much value either. :)
>>
>> IMHO.. an admin wants to see/audit what has been done. How she did it
>> is not relevant.
> [brad] +1

+1 We should store notifications about actions called from CLI/API in 
future. And also add CLI commands for listing notifications.




More information about the katello-devel mailing list