As part of our setup for installing our plugin, our team is looking at adding an additional XML file that contains some configuration information to the plugin.zip file that is servered up to VCenter for loading our plugin. It could be added either along side the plugin.xml file in the zip file or placed in the plugins directory that is in the zip file. This is an XML file that we dynamically generate when our install/configuration process is setting things up.
The question I have is first of all if this would be really frowned upon or if there is a good way of doing this. If I do add the additional XML file to the zip, is there a good way of finding the XML file. I did some experimentation and know that for instance on a linux hosted VCenter server the file ends up in a directory for our plugin under /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/<our plugin dir>/ . How ever using such hard coded paths to find our XML file seems like a bad way to go that has the potential to break in future vSphere releases. ( It also would need to be different for windows systems, so I would need to handle that too).
So my questions is if there is a good way to add an XML file to our zip file that would be supported by the vSphere plugin development guidelines?
Clik here to view.
