VMware audit
The VMware plugin has automated auditing and correcting support from vSphere to Connect. For this purpose, the vSphere configuration is considered the master configuration.
This means:
- if a configuration is missing in Connect but present in vSphere, it is automatically added to Connect
- if a configuration is dangling in Connect and is not present in vSphere, it is automatically removed from Connect
- if a configuration is incorrect in Connect and is present in vSphere, it is automatically updated in Connect
Resources managed by the Fabric Services System are an exception:
- Fabric Services System managed resources are never deleted from Connect
- Fabric Services System managed resources are never updated in Connect
An audit is executed automatically upon any of the following triggers:
- upon starting up the VMware plugin (specifically, upon start-up of the pod in the
Kubernetes cluster) for all deployments that are administratively Up (that is, the
adminUpfield is set to True) - upon creating a new deployment as administratively Up
- upon updating an existing deployment that is administratively Down to be
administratively Up (that is, setting the
adminUpfield to True)
An audit can be triggered manually by sending a POST request to the audits API endpoint (see Audit). If the scope of the request is either PLUGIN_ONLY or FULL, this will include an audit of VMware by the plugin.