Self-service orchestration platform
Techniques for self-service orchestration are disclosed. A system deploys instances of a self-service orchestration agent to tenant-specific software-as-a-service (SaaS) environments operating in a multi-tenant SaaS environment, without reconfiguring existing software in the tenant-specific SaaS environments. Each self-service orchestration agent includes functionality to configure one or more components. Each tenant-specific SaaS environment includes a dedicated set of software operating on a dedicated logical partition of hardware infrastructure. The system receives, via a self-service orchestration interface, a request to configure a component across the tenant-specific SaaS environments. The system: transmits the request to a self-service orchestration module that is operating in the multi-tenant SaaS environment and configured to communicate with each instance of the self-service orchestration agent; dispatches, by the self-service orchestration module, the request to each instance of the self-service orchestration agent; configures, by each of the self-service orchestration agents in a corresponding tenant-specific SaaS environment, the component.
1. One or more non-transitory computer-readable media storing instructions, which when executed by one or more hardware processors, cause performance of operations comprising:
responsive to detecting an executable file in a storage location, identifying a manifest corresponding to the executable file, wherein the manifest identifies (a) a function associated with the executable file and (b) one or more parameter types for one or more parameters of the function;
reading the manifest, to identify (a) the function associated with the executable file and (b) the one or more parameter types for the one or more parameters of the function associated with the executable file;
configuring an interface for accessing the function on a platform, based at least on the one or more parameter types of the function associated with the executable file;
receiving, by the platform via the interface, a command to execute the function associated with the executable file, the command comprising one or more parameter values for the one or more parameters of the function; and
causing execution of the function at least by passing the one or more parameter values to a process corresponding to the executable file.
2. The one or more media of claim 1 , further comprising applying a policy to the process corresponding to the executable file, the policy separate from the executable file and including at least one or more of a security policy, an auditing policy, a communication routing policy, or a life cycle management agent.
3. The one or more media of claim 2 , wherein the policy is associated with an environment within which the process operates.
4. The one or more media of claim 3 , wherein the policy further enables at least one of an auto-configuration function for the process or specifies environment dependencies corresponding to the process.
5. The one or more media of claim 1 , further comprising applying measurement functionality to the process, the measurement functionality identifying at least one of API call sources, API call requests, and measuring request completion times.
6. The one or more media of claim 1 , wherein the manifest further identifies a script in the executable file.
7. The one or more media of claim 1 , wherein the manifest further defines a map identifying at least one script in the executable file and a corresponding function.
8. The one or more media of claim 1 , further comprising inferring an identity of the function associated with the executable file based on one or more of the one or more parameter types and parameters and return values identified in the manifest.
9. The one or more non-transitory computer-readable media of claim 1 , wherein identifying the manifest comprises determining that a particular file comprises one or more keywords indicating that the particular file comprises the manifest.
10. The one or more non-transitory computer-readable media of claim 1 , wherein identifying the manifest corresponding to the executable file comprises identifying, in the executable file, a reference to a location of the manifest.
11. The one or more non-transitory computer-readable media of claim 1 , wherein the manifest is incorporated in the executable file.
12. A method comprising:
identifying a manifest corresponding to an executable file responsive to detecting the executable file in a storage location, wherein the manifest identifies (a) a function associated with the executable file and (b) one or more parameter types for one or more parameters of the function;
reading the manifest, to identify (a) the function associated with the executable file and (b) the one or more parameter types for the one or more parameters of the function associated with the executable file;
configuring an interface for accessing the function on a platform, based at least on the one or more parameter types of the function associated with the executable file;
receiving, by the platform via the interface, a command to execute the function associated with the executable file, the command comprising one or more parameter values for the one or more parameters of the function; and
causing execution of the function at least by passing the one or more parameter values to a process corresponding to the executable file.
13. The method of claim 12 , further comprising applying a policy to the process corresponding to the executable file, the policy separate from the executable file and including at least one or more of a security policy, an auditing policy, a communication routing policy, or a life cycle management agent.
14. The method of claim 13 , wherein the policy is associated with an environment within which the process operates.
15. The method of claim 14 , wherein the policy further enables at least one of an auto-configuration function for the process or specifies environment dependencies corresponding to the process.
16. The method of claim 12 , further comprising applying measurement functionality to the process, the measurement functionality identifying at least one of API call sources, API call requests, and measuring request completion times.
17. The method of claim 12 , wherein the manifest further identifies a script in the executable file.
18. The method of claim 12 , wherein the manifest further defines a map identifying at least one script in the executable file and a corresponding function.
19. The method of claim 12 , further comprising periodically checking a storage location for the executable file.
20. The method of claim 12 , further comprising inferring an identity of the function associated with the executable file based on one or more of the one or more parameter types and parameters and return values identified in the manifest.