diff options
author | Michael DeHaan <mdehaan@redhat.com> | 2008-05-30 11:42:35 -0400 |
---|---|---|
committer | Michael DeHaan <mdehaan@redhat.com> | 2008-05-30 11:42:35 -0400 |
commit | b38dfee242e2b02082cde8f44f6af87a1a243620 (patch) | |
tree | bc1a8d5a8bf01d110ca07d48d65dcd093e97df5a /cobbler/action_replicate.py | |
parent | a63789be503d43b6f4fa42794a18cfe9b8f2c586 (diff) | |
download | third_party-cobbler-b38dfee242e2b02082cde8f44f6af87a1a243620.tar.gz third_party-cobbler-b38dfee242e2b02082cde8f44f6af87a1a243620.tar.xz third_party-cobbler-b38dfee242e2b02082cde8f44f6af87a1a243620.zip |
This change makes triggers that are registered for addition and removal of objects to now run when they are renamed or copied. In the case of a copy, only the add triggers are re-run against the new name. In the case of rename, first the add triggers are called on the newname, then the remove triggers are called on the oldname as that is how things are implemented. In the case of renaming an object that has child objects, the child objects are updated, so the add triggers will then be called on each to notify that those objects themselves have changed, this last bit of the behavior I'm not sure if it's a good thing or not, though we can refine it if that is not desirable.
Diffstat (limited to 'cobbler/action_replicate.py')
0 files changed, 0 insertions, 0 deletions