Infra to Code (I2C) Deployment Guide

Build Continuous Integration (CI)/Continuous Delivery (CD) pipeline for automation of Terraform Execution.
To improve the source code of process.sh and dockerfile, so that it can take in more than the 4 parameters below:
- aws_access_key_id - AWS account ID.
- aws_secret_access_key - AWS account password.
- aws_s3reportbucket - storage destination.
- csp_resources (enhancement) – specify type of resource to be converted.
Copy generated code from S3 bucket and put into a Secure Internet Device and start modification without writing from the start.
To achieve end goal of 100% IaC for Infrastructure provisioning, all Human Accounts for the CSP portal should only grant “ReadOnly” Role, use IaC for any Add/Modify/Delete tasks. This is to avoid configuration drift.
To deploy I₂C static URL frontend portal to run in internet isolated environment. This is to provide more flexibility and security when comes to I₂C deployment.
To improve I₂C to support newer version terraform executable and terraformer, so that I₂C may potentially expand capabilities to support more features / recovering more CSP resources.
To use I₂C as a tool to supplement CSP environment resource configuration backup. For existing and new implementation.
To improve I₂C code base to be used for Azure CSP.
To improve I₂C into an easily deployable infrastructure code so Agency can easily deploy the I₂C on their CSP as required.
Using source code control system, to do versioning on the infrastructure code.