Issue 685275
Created on 2003-02-12 12:25 by jkew, last changed 2021-06-10 01:47 by rouilj.
msg3165 |
Author: [hidden] (jkew) |
Date: 2003-02-12 12:25 |
|
Retiring nodes can have implications down the
line -- see SF bug 685273.
Could roundup-admin be enhanced to make
dealing with retired items easier? Three
suggestions:
a) display <designator> shows the node, retired or
active: would be useful if the display distinguised
retired nodes from active nodes. Possibly a header
on the displayed information:
roundup> display user7
user7 [retired]
-----
username: XX
etc
b) table <class> shows only active nodes of the
class: would be useful to also see retired nodes
and/or see the active/retired status of each.
c) new command unretire <designator> to move a
retired node back into active service.
|
msg5514 |
Author: [hidden] (rouilj) |
Date: 2016-04-10 23:48 |
|
The unretire command already exists as restore.
Would reporting the retired status of the displayed item:
realname: None
retired: yes/no
roles: Admin, Repair
be sufficient?
It looks like internally a retired item has a flag:
__hyperdb_retired
maybe just exposing this would be helpful?
Also searching/find for retired items should be added as well.
|
msg7273 |
Author: [hidden] (rouilj) |
Date: 2021-06-10 01:47 |
|
Consider implementing a command like "option showretired=True"
possible values true/false.
If True all command that would ignore retired items show them with
some indication they are retired. This would affect case b in the
original request and possible find/filter.
See also issue2551103 for another possible use for options command.
|
|
Date |
User |
Action |
Args |
2021-06-10 01:47:39 | rouilj | set | keywords:
+ StarterTicket messages:
+ msg7273 |
2016-04-10 23:48:44 | rouilj | set | nosy:
+ rouilj messages:
+ msg5514 |
2009-03-17 15:04:37 | ajaksu2 | set | nosy:
+ ajaksu2 versions:
+ 1.4 |
2003-02-12 12:25:35 | jkew | create | |
|