http://localhost:8080/gitops_intro/3.change/index.html In this lab we’ll run through a typical infrastructure maintenance process wearing a variety of hats. Specifically we’ll triage a vulnerability found by our security scans, create and assign a ticket to track resolution of the issue, and update our deployment in order to actually fix the problem. Finally we’ll use our CI/CD pipeline to automatically run new scans and deploy our updated infrastructure. Key Terms Vulnerability - A weakness in system configuration that could be exploited Issue - A convenient way to document and track a software request Commit - Save a code change to our source control repository Hugo en-us Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/gitops_intro/3.change/analyze/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/gitops_intro/3.change/analyze/index.html Open the vulnerability report Accept our security finding and log an issue. Drill into our critical vulnerability Confirm the vulnerability Open a ticket http://localhost:8080/gitops_intro/3.change/document/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/gitops_intro/3.change/document/index.html Review the open tickets Load our open ticket Make it someone else’s problem http://localhost:8080/gitops_intro/3.change/develop/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/gitops_intro/3.change/develop/index.html Open the built-in developer environment Delete the AWS credentials file Review and commit our change http://localhost:8080/gitops_intro/3.change/resolve/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/gitops_intro/3.change/resolve/index.html As the PM … let’s open our ticket back up review who closed the issue and how Call the buildmaster … now let’s open the pipeline and deploy our updated application