Script Runtime Service for vSphere (SRS) enables vSphere users and services (clients) to manage PowerCLI instances and run PowerCLI scripts. SRS clients authenticate once with vSphere credentials or access token. SRS clients create PowerCLI instances and run scripts within. PowerCLI runs server-side and automatically connects to the target vCenter Servers. SRS tracks history of script outputs.
- Central place with REST API endpoint for VI Admins to run VMware PowerCLI
- Manage multiple PowerCLI instances to run commands and scripts against vCenter Servers without calling Connect-VIServer
- Interactive WebConsole to a PowerCLI instance
- Runs on Kubernetes
Install on a VM
Install on a Kubernetes Cluster
Getting Started with SRS API
API Reference
Swagger Codegen can be used to generate client side SDKs for different languages.
Java and C# example client applications based on auto-generated client-side SDKs are available in OpenAPI Clients.
Check the vision and what's coming next
The script-runtime-service-for-vsphere project team welcomes contributions from the community. If you wish to contribute code and you have not signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For any questions about the CLA process, please refer to our FAQ. For more detailed information, refer to CONTRIBUTING.md.
The repo is in very early stage for contributors. A lot of documentation is pending to be created. Until it is done you can use the script-runtime-service-assist channel on VMware Code slack
- Join VMware Code
- Join the following channel:
script-runtime-service-assist
Script Runtime Service for vSphere is distributed under the Apache 2.0.
For more details, please refer to the Apache 2.0 License File.