# US 2019/0318312 A1 · Infrastructure validation architecture for serverless execution frameworks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0318312 A1 - Document ID: US20190318312A1 - Status: Published application - Kind: A1 - Application number: 16/441,627 - Filed: 2019-06-14 - Published: 2019-10-17 - Earliest claimed: 2017-09-08 - Assignees: Accenture Global Solutions Limited - Applicants: Accenture Global Solutions Limited - Inventors: Roger Foskett; Thomas W. Myers - Web page: https://patentgrep.com/patent/US20190318312A1 ## CPC - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F 8/70: Software maintenance or management - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 9/5011: {the resources being hardware resources other than CPUs, Servers and Terminals} - G06F 9/5072: {Grid computing} - G06F 9/547: {Remote procedure calls [RPC]; Web services} - G06F 11/3668: Testing of software - G06Q 10/101: Collaborative creation, e.g. joint development of products or services - G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Successfully deploying resources into the cloud is a constantly increasing technical challenge as more cloud service providers emerge, each offering disparate computing platforms, services, assets, supported technical components, and other features, including serverless execution. An infrastructure build and collaboration architecture for serverless execution environments solves the technically complex challenges around allowing developers to work independently in physically separated locations. To this end, the architecture allows shared object repositories to be brought together when required. The architecture performs deep validation of the infrastructure built for the developer. ## Claims ### Claim 1 A system including: a physical communication interface configured to implement a communication channel to a serverless infrastructure provider; hardware data storage configured to store: an infrastructure definition within an infrastructure directory; and a test definition associated with the infrastructure definition, the test definition including an enablement flag; and validation hardware circuitry configured to: load the infrastructure definition from the infrastructure directory; based on the enablement flag, determine whether the test definition is enabled or non-enabled; exclude the test definition when the test definition is not enabled; generate a call to the serverless infrastructure provider when the test definition is enabled, the call configured to request a resource description for a provisioned resource; receive a resource description in response to the call; responsive to the resource description, execute an expression query on the resource description to determine whether the resource description includes an expected configuration; terminate the provisioned resource when the expected configuration is not included within the resource description; and mark the infrastructure definition as validated when the expected configuration is included within the resource description. ### Claim 2 (depends on 1) The system of claim 1, where the validation circuitry is further configured to: check whether the test definition was excluded; and report an error to an operator interface display when the test definition was excluded. ### Claim 3 (depends on 1) The system of claim 1, where the validation circuitry is further configured to report an error to an operator interface display when the expected configuration is not included within the resource description. ### Claim 4 (depends on 1) The system of claim 1, where the expected configuration includes: a specific hash attribute, a specific range attribute, or both. ### Claim 5 (depends on 1) The system of claim 1, where the expected configuration includes a specific table type. ### Claim 6 (depends on 1) The system of claim 1, where the system further includes instantiation engine circuitry configured to: initiate instantiation of the provisioned resource; and cause invocation of the validation circuitry in response to initiation of the instantiation of the provisioned resource. ### Claim 7 (depends on 1) The system of claim 1, where the resource description includes: a resource presence indication for the provisioned resource; and a detail status descriptor of provisioning status for the provisioned resource. ### Claim 8 (depends on 1) The system of claim 1, where the call includes a software development kit (SDK) call, a command line interface command, or both. ### Claim 9 (depends on 1) The system of claim 1, where the validation circuitry is configured to operate on each of multiple infrastructure definitions in the infrastructure directory. ### Claim 10 (depends on 1) The system of claim 1, where the infrastructure definition includes: a yet another markup language (YAML) file; a comma separated value (CSV) file; a javascript object notation (JSON) file; or any combination of the foregoing. ### Claim 11 A method including: at a physical communication interface, implementing a communication channel to a serverless infrastructure provider; and at validation hardware circuitry: loading an infrastructure definition from an infrastructure directory, the infrastructure directory stored within hardware data storage along with a test definition associated with the with the infrastructure definition; based on an enablement flag included within the test definition, determining whether the test definition is enabled or non-enabled; excluding the test definition when the test definition is not enabled; generating a call to the serverless infrastructure provider when the test definition is enabled, the call configured to request a resource description for a provisioned resource; receiving a resource description in response to the call; responsive to the resource description, executing an expression query on the resource description to determine whether the resource description includes an expected configuration; terminating the provisioned resource when the expected configuration is not included within the resource description; and marking the infrastructure definition as validated when the expected configuration is included within the resource description. ### Claim 12 (depends on 11) The method of claim 11, further including: at the validation circuitry: checking whether the test definition was excluded; and reporting an error to an operator interface display when the test definition has been excluded. ### Claim 13 (depends on 11) The method of claim 11, further including, at the validation circuitry, report an error to an operator interface display when the expected configuration is not included within the resource description. ### Claim 14 (depends on 11) The method of claim 11, where the expected configuration includes: a specific hash attribute, a specific range attribute, or both. ### Claim 15 (depends on 11) The method of claim 11, where the expected configuration includes a specific table type. ### Claim 16 A product including: machine-readable media other than a transitory signal; and instructions stored on the machine-readable media, the instructions configured to, when executed, cause a machine to: at a physical communication interface, implement a communication channel to a serverless infrastructure provider; and at validation hardware circuitry: load an infrastructure definition from an infrastructure directory, the infrastructure directory stored within hardware data storage along with a test definition associated with the with the infrastructure definition; based on an enablement flag included within the test definition, determine whether the test definition is enabled or non-enabled; exclude the test definition when the test definition is not enabled; generate a call to the serverless infrastructure provider when the test definition is enabled, the call configured to request a resource description for a provisioned resource; receive a resource description in response to the call; responsive to the resource description, execute an expression query on the resource description to determine whether the resource description includes an expected configuration; terminate the provisioned resource when the expected configuration is not included within the resource description; and mark the infrastructure definition as validated when the expected configuration is included within the resource description. ### Claim 17 (depends on 16) The product of claim 16, instructions are further configured to cause the machine to: at instantiation engine circuitry: initiate instantiation of the provisioned resource; and cause invocation of the validation circuitry in response to initiation of the instantiation of the provisioned resource. ### Claim 18 (depends on 16) The product of claim 16, where the resource description includes: a resource presence indication for the provisioned resource; and a detail status descriptor of provisioning status for the provisioned resource. ### Claim 19 (depends on 16) The product of claim 16, where the call includes a software development kit (SDK) call, a command line interface command, or both. ### Claim 20 (depends on 16) The product of claim 16, where the infrastructure definition includes: a yet another markup language (YAML) file; a comma separated value (CSV) file; a javascript object notation (JSON) file; or any combination of the foregoing.