# US 12,602,256 B2 · Process invocation responsive to configuration deployment > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,256 B2 - Document ID: US12602256B2 - Status: Granted - Kind: B2 - Application number: 17/730,573 - Filed: 2022-04-27 - Published: 2023-11-02 - Granted: 2026-04-14 - Earliest claimed: 2022-04-27 - Assignees: Micro Focus LLC - Applicants: Micro Focus LLC - Inventors: Steve Berube; Christopher Schleicher; Michael David Oba - Web page: https://patentgrep.com/patent/US12602256B2 ## CPC - G06F 9/5044: {considering hardware capabilities} - G06F 9/5033: {considering data affinity} - G06F 9/5038: {considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups)} - G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)} - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A controller system receives from a deployer for a computing resource and into which the controller system has been hooked, a state of the computing resource resulting from deployment of a configuration on the computing resource by a deployment user using the deployer. In response to receiving the state of the computing resource from the deployer, the controller system persists the state within a database. In response to receiving the state of the computing resource from the deployer, the controller system automatically invokes a process previously defined by a process user and maintained by a process system into which the controller system has been hooked, based on the state. ## Claims ### Claim 1 A non-transitory computer-readable data storage medium storing program code executable by a controller system to perform processing comprising: receiving, by the controller system and from a deployer for a computing resource and into which the controller system has been hooked, a state of the computing resource resulting from a deployment of a configuration on the computing resource by a deployment user using the deployer, wherein the deployer deploys the configuration on the computing resource without interaction with the controller system, wherein the deployment of the configuration on the computing resource is disassociated from promulgation of a policy specified by a process previously defined by a process user and maintained by a process system into which the controller system has also been hooked, wherein the deployer, the process system, and the controller system are each discrete and different from one another, and the process user and the deployment user are different users, wherein the policy pertains to which configurations are permissible for deployment on the computing resource, and the configuration deployed on the computing resource using the deployer is not permitted by the policy; and in response to the controller system receiving the state of the computing resource from the deployer, persisting, by the controller system, the state within a database maintained by the controller system, and automatically invoking the process based on the state, based on the state, wherein automatically invoking the process comprises: initiating a compliance check according to the policy to determine that the deployment of the configuration on the computing resource is not permitted; and in response to determining that the deployment of the configuration on the computing resource is not permitted, initiating rollback of the computing resource to a prior state of the computing resource previously persisted within the database, wherein hooking of the controller system into both the deployer and the process system ensures that, as a result of the controller system initiating rollback of the computing resource to the prior state, the configuration is ultimately not deployed on the computing resource, even though the deployment of the configuration on the computing resource is otherwise disassociated from promulgation of the policy since the deployer and the process system do not communicate with one another. ### Claim 2 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein automatically invoking the process further comprises: initiating one or more subscriptions specified by the process to the state, wherein the subscriptions comprise either or both of: notification subscriptions to notify other users of the deployment of the configuration on the computing resource resulting in the state; and reporting subscriptions to cause the state of the computing resource resulting from the deployment of the configuration to be included in future reports. ### Claim 3 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein automatically invoking the process further comprises: initiating calculation of a cost of the state of the computing resource resulting from the deployment of the configuration; and persisting the cost of the state of the computing resource within the database. ### Claim 4 (depends on 3) The non-transitory computer-readable data storage medium of claim 3, wherein automatically invoking the process further comprises: initiating the compliance check according to the policy specified by the process to determine whether the deployment of the configuration on the computing resource was permitted, based on the cost of the state of the computing resource resulting from the deployment of the configuration. ### Claim 5 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein the processing further comprises: in response to receiving, from the process system into which the controller system has been hooked, an indication that the process has changed, automatically reinvoking the process based on the state. ### Claim 6 (depends on 5) The non-transitory computer-readable data storage medium of claim 5, wherein automatically reinvoking the process based on the state comprises: initiating the compliance check according to the policy specified by the process and that has been updated since the deployment of the configuration on the computing resource, to determine whether the deployment was permitted, based on the state. ### Claim 7 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein the controller system is hooked into the deployer such that how the deployment user interacts with the deployer to deploy the configuration on the computing resource is unchanged. ### Claim 8 A computing system comprising: a storage device storing a database; a processor; and a memory storing controller program code that has been hooked into a deployer for a computing resource and into a process system maintaining a process that has been previously defined by a process user and that pertains to the computing resource, and that is executable by the processor to: receive, by the controller program code from the deployer due to the controller program code having been hooked into the deployer, a state of the computing resource resulting from a deployment of a configuration on the computing resource by a deployment user using the deployer, wherein the deployer deploys the configuration on the computing resource without interaction with a controller system, wherein the deployment of the configuration on the computing resource is disassociated from promulgation of a policy specified by the process, wherein the deployer, the process system, and the controller system are each discrete and different from one another, and the process user and the deployment user are different users, wherein the policy pertains to which configurations are permissible for deployment on the computing resource, and the configuration deployed on the computing resource using the deployer is not permitted by the policy; and in response to the controller program code receiving the state of the computing resource from the deployer, persist the state within the database maintained by the controller program code, and automatically invoke the process based on the state, wherein the controller program code is executable by the processor to automatically invoke the process based on the state by: initiating a compliance check according to the policy specified by the process to determine that the deployment of the configuration on the computing resource is not permitted; and in response to determining that the deployment of the configuration on the computing resource is not permitted, initiating rollback of the computing resource to a prior state of the computing resource previously persisted within the database, wherein hooking of the controller system into both the deployer and the process system ensures that, as a result of the controller system initiating rollback of the computing resource to the prior state, the configuration is ultimately not deployed on the computing resource, even though the deployment of the configuration on the computing resource is otherwise disassociated from promulgation of the policy since the deployer and the process system do not communicate with one another. ### Claim 9 (depends on 8) The computing system of claim 8, wherein the controller program code is hooked into the deployer in a reaction model that employs a trigger that causes the state resulting from the deployment of the configuration on the computing resource to be automatically transmitted to the controller program code from a backend system on which the deployer is implemented, and wherein automatic transmission of the state to the controller program code is transparent to the deployer. ### Claim 10 (depends on 8) The computing system of claim 8, wherein the controller program code is hooked into the deployer in a first class model by which the deployer does not have an existing backend component and a backend component is added to the deployer to cause the deployer to automatically push the state resulting from the deployment of the configuration on the computing resource to the controller program code. ### Claim 11 (depends on 8) The computing system of claim 8, wherein the controller program code is hooked into the deployer in a sidecar model by which the deployer has an existing backend component that receives the state resulting from the deployment on the computing resource, and by which a sidecar component is added to the existing backend component to additionally push the state to the controller program code. ### Claim 12 (depends on 8) The computing system of claim 8, wherein the controller program code is executable by the processor to automatically invoke the process by further: initiating one or multiple notification subscriptions to notify process-specified users of the deployment of the configuration on the computing resource resulting in the state; and initiating one or multiple reporting subscriptions to cause the state of the computing resource resulting from the deployment of the configuration to be included in future reports. ### Claim 13 (depends on 8) The computing system of claim 8, wherein the controller program code is executable by the processor to automatically invoke the process by: initiating calculation of a cost of the state of the computing resource resulting from the deployment of the configuration; persisting the cost of the state of the computing resource within the database; and initiating the compliance check according to the policy specified by the process to determine whether the deployment of the configuration on the computing resource was permitted, based on the cost of the state of the computing resource resulting from the deployment of the configuration. ### Claim 14 (depends on 8) The computing system of claim 8, wherein the controller program code is executable by the processor to further: receive, from the process system due to the controller program code having been hooked into the process system, an indication that the process has been changed; and in response to receiving the indication that the process has been changed, automatically reinvoke the process based on the state. ### Claim 15 A method comprising: receiving, by a controller system from a deployer for a computing resource and into which the controller system has been hooked, a state of the computing resource resulting from a deployment of a configuration on the computing resource by a deployment user using the deployer, wherein the deployer deploys the configuration on the computing resource without interaction with the controller system, wherein the deployment of the configuration on the computing resource is disassociated from promulgation of a policy specified by a process previously defined by a process user and maintained by a process system into which the controller system has also been hooked, wherein the deployer, the process system, and the controller system are each discrete and different from one another, and the process user and the deployment user are different users, wherein the policy pertains to which configurations are permissible for deployment on the computing resource, and the configuration deployed on the computing resource using the deployer is not permitted by the policy; and in response to the controller system receiving the state, persisting, by the controller system, the state within a database maintained by the controller system, and automatically invoking, the process based on the state, wherein automatically invoking the process comprises: initiating a compliance check according to the policy to determine that the deployment of the configuration on the computing resource is not permitted; and in response to determining that the deployment of the configuration on the computing resource is not permitted, initiating rollback of the computing resource to a prior state of the computing resource previously persisted within the database, wherein hooking of the controller system into both the deployer and the process system ensures that, as a result of the controller system initiating rollback of the computing resource to the prior state, the configuration is ultimately not deployed on the computing resource, even though the deployment of the configuration on the computing resource is otherwise disassociated from promulgation of the policy since the deployer and the process system do not communicate with one another. ### Claim 16 (depends on 15) The method of claim 15, further comprising: in response to receiving, by the controller system from the process system into which the controller system has been hooked, an indication that the process has been changed, automatically reinvoking, by the controller system, the process based on the state, wherein automatic reinvocation of the process includes reinitiation of the compliance check according to the policy specified by the process and that has been updated since the deployment of the configuration on the computing resource, to determine whether the deployment was permitted, based on the state. ### Claim 17 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein the controller system is hooked into the deployer in a reaction model that employs a trigger that causes the state resulting from the deployment of the configuration on the computing resource to be automatically transmitted to the controller system from a backend system on which the deployer is implemented, and wherein automatic transmission of the state to the controller system is transparent to the deployer. ### Claim 18 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein the controller system is hooked into the deployer in a first class model by which the deployer does not have an existing backend component and a backend component is added to the deployer to cause the deployer to automatically push the state resulting from the deployment of the configuration on the computing resource to the controller system. ### Claim 19 (depends on 1) The non-transitory computer-readable data storage medium of claim 1, wherein the controller system is hooked into the deployer in a sidecar model by which the deployer has an existing backend component that receives the state resulting from the deployment on the computing resource, and by which a sidecar component is added to the existing backend component to additionally push the state to the controller system.