New VMware modules dropped

Let me illustrate the complexity of integrating these updates with existing stuff:

1. I have to have the exchange (not the module toolbox?) pulled up to know if a module is new or existing (could have just been signaled in the docs).
2. I have to have the documentation pulled up to know which modules replace which modules.
3. I have to have the module toolbox pulled up so I can pull in the changes.
4. I have to search through all my groups for custom thresholds that I have to recreate on the new modules, but I can’t do that until they’re imported. And searching for custom thresholds is made more complicated by the fact that on the alert tuning tab they are displayed by display name, not name. The documentation uses name (rightly so), so knowing which one is which requires me to also look up the module in the repo/toolbox. I can run a report, but those have become less and less reliable with the new schedule-now bug.
5. I also have to identify all the customizations that we’ve done to the existing modules and apply those to the new modules, which I can’t do until I’ve already pulled the new modules into prod, by which time, they’re already alerting with non-custom alert thresholds, trigger/clear interval settings, discovery customizations, etc..

Forgive me for being a little salty, but this isn’t something that we can just import and see how it goes. The existing modules weren’t tuned for reality/usability, so we had to make significant modifications to get them to work well in a real environment.