Infrastructure quality assurance framework

Patent metadata

Field	Value
Publication number	US-12360880-B2
Application number	US-202418734726-A
Country	US
Kind code	B2
Filing date	Jun 5, 2024
Priority date	Nov 3, 2021
Publication date	Jul 15, 2025
Grant date	Jul 15, 2025

Abstract

Systems and methods for providing an automated quality assurance framework for infrastructure as code (“IaC”) implementations are provided. Pull requests with proposed change to existing IaC source code (“changed code”) are received from user devices, each associated with either a service enablement team member or an applications development team member. Team specific versions of the quality assurance framework are automatically triggered for the changed code which require successful passage through multiple modules, such as in a successive manner, before automatically being merged into the existing IaC source code.

First claim

What is claimed is:

1. A method for providing an automated quality assurance framework for infrastructure as code (“IaC”) implementations, said method comprising the steps of:
electronically receiving a pull request associated with a proposed change to existing IaC source code (“changed code”) from a device identified as associated with one of: a service enablement team member and an applications development team member;
where said pull request originates from a device indicated as associated with the service enablement team member, electronically and automatically:
applying a naming and documentation check module to the changed code which compares names in the changed code against a database of names for a match and verifies that updates have been made to an electronic log;
applying a coding standards check module to the changed code which verifies that predetermined syntax standards are adhered to in the changed code; and
applying a test case and security check module to the changed code which verifies that a predetermined test case is executable in the changed code and that configurations are utilized in the changed code; and

where said pull request originates from a device indicated as associated with the applications development team member, electronically and automatically:
applying an infrastructure validations module to the changed code which compares at least part of the changed code against at least some aspects of a prior version of the existing IaC source code;
applying a coding standards and compliance check module to the changed code which verifies that predetermined standards present in the changed code; and
applying the test case and security check module to the changed code.

2. The method of claim 1 further comprising:
creating a new working code area within said a source code repository for temporary storage of said changed code for each of said pull requests;
upon receipt of data indicating successful completion of the quality assurance framework, automatically and electronically merging the changed code into the existing IaC source code;
generating a failure notification where the quality assurance framework associated with the respective one of the pull requests is not successfully passed; and
transmitting the respective one of the failure notifications to a user device from which the respective one of the pull requests is indicated as originating, wherein each of said failure notifications comprise an indication of which portion of said quality assurance framework was not successfully passed for said respective one of said pull requests.

3. The method of claim 2 wherein:
said step of merging the changed code into the existing IaC source code comprises:
creating a new release; and
tagging the changed code with a new tag.

4. The method of claim 1 further comprising:
triggering a manual review of the changed code.

5. The method of claim 1 wherein:
said naming and documentation check module comprises:
a branch naming standards module which compares branch names used against a database of predetermined, acceptable naming standards; and
a documentation check module which verifies that modifications have been made to a change log file.

6. The method of claim 1 wherein:
said coding standards check module comprises:
a parameter syntax check module which verifies that variable types and descriptions are provided; and
a provider syntax check module which verifies that specific provider configuration fields are provided.

7. The method of claim 1 wherein:
said test case and security check module comprises:
a predefined test cases module which applies a predefined test case simulating deployment or use to the changed code; and
a security check module which verifies that certain predetermined, recommended security configurations are utilized in the changed code.

8. The method of claim 1 wherein:
the infrastructure validations module comprises a day zero infrastructure comparison module which compares the changed code against a prior version of the existing IaC source code values provided by a user.

9. The method of claim 1 wherein:
the coding standards and compliance check module comprises:
a lifecycle check module which verifies that an up-to-date tag is provided with the changed code;
a parameter value check module which verifies that certain predetermined disaster recommendations are followed; and
a provider syntax check module which compares the changed code against a database of acceptable syntax.

10. The method of claim 1 wherein:
said naming and documentation check module comprises:
a branch naming standards module which compares branch names used against a database of predetermined, acceptable naming standards; and
a documentation check module which verifies that modifications have been made to a change log file;

said coding standards check module comprises:
a parameter syntax check module which verifies that variable types and descriptions are provided; and
a provider syntax check module which verifies that specific provider configuration fields are provided;

said test case and security check module comprises:
a predefined test cases module which applies a predefined test case simulating deployment or use to the changed code; and
a security check module which verifies that certain predetermined, recommended security configurations are utilized in the changed code;

the infrastructure validations module comprises a day zero infrastructure comparison module which compares the changed code against a prior version of the existing IaC source code values provided by a user; and
the coding standards and compliance check module comprises:
a lifecycle check module which verifies that an up-to-date tag is provided with the changed code;
a parameter value check module which verifies that certain predetermined disaster recommendations are followed; and
a provider syntax check module which compares the changed code against a database of acceptable syntax.

11. A system for providing an automated quality assurance framework for infrastructure as code (“IaC”) implementations, said system comprising:
an IaC source code repository storing existing IaC source code;
user devices, a first of which is associated with an applications development team member, and a second of which is associated with a service enablement team member;
one or more electronic storage devices comprising software instructions, which when executed, configure one or more processors to:
receive pull requests, each associated with a proposed change to the existing IaC source code (“changed code”) and indicated as originating from the first one or the second one of the user devices;
where a respective one of the pull requests is indicated as originating from the first one of the user devices:
apply a naming and documentation check module to the changed code which compares certain names in the changed code against a database of names for a match and verify that updates have been made to a certain log when applied;
apply a coding standards check module to the changed code which verifies that certain predetermined syntax standards are adhered to in the changed code when applied; and
apply a test case and security check module to the changed code which verifies that at least one predetermined test case is executable in the changed code and that certain configurations are utilized in the changed code when applied;

where the respective one of the pull requests is indicated as originating from the second one of the user devices:
apply an infrastructure validations module to the changed code which compares at least part of the changed cod

Assignees

• Humana Inc

Inventors

• Chivukula Srirama Murthy
• Chintakayala Mohan
• Singh Sumit Kumar
• Meyer Keith Hamilton
• Beasey Stephen

Classifications

• G06F21/577 Primary

  Assessing vulnerabilities and evaluating computer system security · CPC title

• G06F11/3688

  for test execution, e.g. scheduling of test suites · CPC title

• G06F2221/033

  Test or assess software · CPC title

• G06F8/73

  Program documentation · CPC title

• G06F11/3604

  Analysis of software for verifying properties of programs (testing of software G06F11/3668) · CPC title