for alot of zenpacks I end up moving around the events into event classes/event class instances that conform to our general schema for event management. usually the first time we install a zenpack we will allow the zenpack to install its event class/event class key/instances but after that we have typically customized things and when you update the zenpack it creates duplicates that we have to delete either via scripts or manually for smaller zenpacks.
would love the option to install a zenpacklib zenpack with a --skip_events option. For example the enterprise cisco zenpack creates a tone of eventClass instances...the cisco ucs one messes with out default mapping order etc..
its easier for us to diff out the changes and add them manually or via our own events zenpack or handle it some other way than to install and go through a massive cleanup..another example is the hp enterprise zenpack we have alot of the hp traps parsed with a bunch of lessons learned and having duplicates that may have lower or higher sequence numbers messes with things big time.
ive taken to removing he events sections of the yaml or objects.xml and re-zipping the egg as part of a build process for zenpacks but it would be cleaner to just install them excluding the events part of the yaml...
for alot of zenpacks I end up moving around the events into event classes/event class instances that conform to our general schema for event management. usually the first time we install a zenpack we will allow the zenpack to install its event class/event class key/instances but after that we have typically customized things and when you update the zenpack it creates duplicates that we have to delete either via scripts or manually for smaller zenpacks.
would love the option to install a zenpacklib zenpack with a --skip_events option. For example the enterprise cisco zenpack creates a tone of eventClass instances...the cisco ucs one messes with out default mapping order etc..
its easier for us to diff out the changes and add them manually or via our own events zenpack or handle it some other way than to install and go through a massive cleanup..another example is the hp enterprise zenpack we have alot of the hp traps parsed with a bunch of lessons learned and having duplicates that may have lower or higher sequence numbers messes with things big time.
ive taken to removing he events sections of the yaml or objects.xml and re-zipping the egg as part of a build process for zenpacks but it would be cleaner to just install them excluding the events part of the yaml...