Repository services enable the vA 320 to operate a repository such as, the repository 134 of FIG. 1. In this manner, the repository 134 may be implemented within the deployment environment 112 (e.g., as a component of the vA 320) and/or external to the deployment environment 112. Implementing the repository 134 within the deployment environment 112 enables an administrator 116 of the deployment environment 112 to host instructions for execution at monitoring agents within the deployment environment. In this manner, an administrator can implement configurations that are specific to their deployment environment 112 without having to reference a third party and/or publicly available repository. In contrast, in some examples, the repository 134 may be hosted outside of the deployment environment 112 (e.g., within another deployment environment hosted by the cloud provider 110, outside of the control of the cloud provider 110, etc.) Implementing the repository 134 outside of the deployment environment 112 enables the administrator 116 to configure the management endpoint 340 to instruct one or more management endpoints 350 to retrieve and/or execute instructions hosted by a third party (e.g., a developer, a professional services organization (PSO), a publicly available website, etc.). Such an approach is useful when a third party provides instructions (e.g., executables) that may be updated by the third party.
The example event broker 430 provides a mechanism to handle tasks which are transferred between services with the orchestrator 420. The example authentication provider 440 (e.g., VMware Horizon? services, etc.) authenticates access to services and data, for example.
