Testing changes in Isolation - Build Temp-Dynamic & Disposable Pull-Request FE/UI Environments
<p>On this Post I will tackle the following problem by <strong>Building Temporary-Dynamic & Disposable Pull-Request Front-End Portal UIs Environments </strong>using <strong>Terraform, Terragrunt, AWS, CloudFront, Route53</strong> <strong>and S3</strong>.</p>
<p>T<strong>he Problem</strong>: When starting a new Project, We Deploy the necessary infrastructure using <a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-aws-environment/understanding-landing-zones.html" rel="noopener ugc nofollow" target="_blank">AWS Landing-Zone</a> best practices. Creating different AWS accounts under the same <a href="https://aws.amazon.com/organizations/" rel="noopener ugc nofollow" target="_blank">AWS Organization</a> for each of our environments. T<a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-aws-environment/understanding-landing-zones.html" rel="noopener ugc nofollow" target="_blank">his has a lot of advantages</a>.</p>
<p><strong>But still we only have 1 Single Test environment and </strong>Testing 1 thing at the time is not scalable.</p>
<p>T<strong>he Queue of changes start increasing and Testing a Pull request becomes a bottle neck. </strong>Pull Requests will start piling up, at some point there can be a risk of someone deploying to the test Feature-B while Feature-A was in testing. Dus creating confusion and frustration.</p>
<p><a href="https://awstip.com/testing-changes-in-isolation-build-temp-dynamic-disposable-pull-request-environments-for-fe-ui-2cfbc3060a8a"><strong>Click Here</strong></a></p>