core-admin/qubes/vm
Marek Marczykowski-Górecki 50d34755fa
vm: include tag/feature name in event name
Rename events:
 - domain-feature-set -> domain-feature-set:feature
 - domain-feature-delete -> domain-feature-delete:feature
 - domain-tag-add -> domain-tag-add:tag
 - domain-tag-delete -> domain-tag-delete:tag

Make it consistent with property-* events. It makes more sense to
include tag/feature name in event name, so handler can watch a single
tag/feature - which is the most common case. Otherwise, most handlers
would begin with `if feature == '...'` anyway, wasting time on most
events.

In cases where multiple features/tags should be handled by a single
handler, it is now possible to register a handler with wildcard, for
example `domain-feature-set:*`.
2018-01-06 15:05:34 +01:00
..
mix Make pylint happy 2017-12-21 18:19:10 +01:00
__init__.py vm: include tag/feature name in event name 2018-01-06 15:05:34 +01:00
adminvm.py vm/adminvm: fix type of AdminVM.qid 2017-12-21 18:18:12 +01:00
appvm.py Change license to LGPL v2.1+ 2017-10-12 00:11:50 +02:00
dispvm.py qubes/vm: Improve stopped event handling 2017-10-21 05:57:57 +02:00
qubesvm.py vm: include tag/feature name in event name 2018-01-06 15:05:34 +01:00
standalonevm.py Change license to LGPL v2.1+ 2017-10-12 00:11:50 +02:00
templatevm.py Change license to LGPL v2.1+ 2017-10-12 00:11:50 +02:00