ZEN-29068: For upgrades, a separate log file needs to be generated fo… #543
Conversation
…r Monitoring Template changes/conflicts/remediations
There was a problem hiding this comment.
I'd like to take some time to review this, since this particular part of ZPL has had numerous revisions and is a bit tricky. My intent has been to move all of the "audit" code into a separate class since it gets used elsewhere in ZPL (and in unit tests) and also because it complicates the ZenPack class unnecessarily. Unless there's a pressing need to have this in the hotfix branch, my inclination would be to make these changes to develop, especially since (as you noted in JIRA) there are several different scenarios (upgrades from legacy or ZPL1, for example), that come into play as well.
|
Another thought -- if this is a particular pain point for vSphere ZP, what about making these changes in a ZenPack class override in the vSphere ZP init (ZenPack) class? |
|
The request was to save all templates' diffs into a separate place. This is not related only to vSphere ZP. |
|
please see #544 |
|
Would be nice to be able to duel log all zplib commamds to a separate log thst is set to go to kibana. Also be able to have it use a different level of severity than what goes to stdout. When i install a zenpack i just want to know if tgerr are errors amd it should be essy to see then refer to a detailed log for details om success or failure. Also there is no clesr indicator that a zp sucrssfully installed and the errored output usually makes it clear something went wrong but its inconsistent so i find auromating it with a lipeline and checking for failures to be difficult |
No description provided.