Lewis Lampkin, III

This post is part of a 5-post series on setting up version control in the cloud using AWS Code Commit (cloud repository), Git (version control) and AWS Cloud 9 (Cloud IDE). Part 1 of 5: AWS Code Commit: Creating Git repositories Part 2 of 5: AWS Code Commit: Infrastructure/Devops Engineer Setup Part 3 of 5: AWS Code Commit: Software Developer #1 Part 4 of 5: AWS Code Commit: Software Developer #2 Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference Here is the cleanup, evidence, and references for the prior 4 parts. After Scott saved the day, the Devops Engineer decided to clean up the environments up. The engineer also took some screenshots as evidence of the environment cleanup, because he knew the pointy-haired team lead didn't read much and enjoyed looking at pictures. Even though Mr. Pointy Hairs doesn't read, the Devops Engineer knew that the lead liked reference links, so the engineer included a link to the vendor documentation on integrating AWS Cloud9 with

This post is part of a 5-post series on setting up version control in the cloud using AWS Code Commit (cloud repository), Git (version control) and AWS Cloud 9 (Cloud IDE). Part 1 of 5: AWS Code Commit: Creating Git repositories Part 2 of 5: AWS Code Commit: Infrastructure/Devops Engineer Setup Part 3 of 5: AWS Code Commit: Software Developer #1 Part 4 of 5: AWS Code Commit: Software Developer #2 Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference After Radia (aka Developer #1) went on vacation, the pointy-haired team lead spotted the mistake Mr. Snuggles sneaked into production and demanded that the problem be fixed as soon as possible (ASAP)! Scott (aka Developer #2) recently led the software design effort for next generation voting software that relies on blockchain technology to log all votes and related data so that recounts are instantaneous and to prevent single points of failure in the voting infrastructure. While that has absolutely nothing to do with Hum

This post is part of a 5-post series on setting up version control in the cloud using AWS Code Commit (cloud repository), Git (version control) and AWS Cloud 9 (Cloud IDE). Part 1 of 5: AWS Code Commit: Creating Git repositories Part 2 of 5: AWS Code Commit: Infrastructure/Devops Engineer Setup Part 3 of 5: AWS Code Commit: Software Developer #1 Part 4 of 5: AWS Code Commit: Software Developer #2 Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference The task for the development team is to get the index.html for HumanGov Proof-of-Concept up right away. The best developer on the team, Radia, is assigned the task, and she whips up the solution after just a few minutes and informs the team lead. Radia is so good that everyone just calls her developer #1. Radia is now packing her bags, as she is going to be a guest speaker at the Grace Hopper Conference. Of course, the lead decided as Radia was about to shut down for the day that the header size that had been signed of

This post is part of a 5-post series on setting up version control in the cloud using AWS Code Commit (cloud repository), Git (version control) and AWS Cloud 9 (Cloud IDE). Part 1 of 5: AWS Code Commit: Creating Git repositories Part 2 of 5: AWS Code Commit: Infrastructure/Devops Engineer Setup Part 3 of 5: AWS Code Commit: Software Developer #1 Part 4 of 5: AWS Code Commit: Software Developer #2 Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference The DevOps Engineer is tasked with being able to maintain the infrastructure and assist with any applications issues. For this reason, the DevOps engineer needs to be able to update the infrastructure and application repositories. 2.1: Configure Git username and email git config --global user.name "Lewis Lampkin, III - Infrastructure/DevOps Engineer" git config --global user.email "lewis.lampkin@humangov.com" 2.2: Configure AWS CLI Credential Helper git config --global credential.helper '!aws

This post is part of a 5-post series on setting up version control in the cloud using AWS Code Commit (cloud repository), Git (version control) and AWS Cloud 9 (Cloud IDE). Part 1 of 5: AWS Code Commit: Creating Git repositories Part 2 of 5: AWS Code Commit: Infrastructure/Devops Engineer Setup Part 3 of 5: AWS Code Commit: Software Developer #1 Part 4 of 5: AWS Code Commit: Software Developer #2 Part 5 of 5: AWS Code Commit: Cleanup, Evidence, Reference Per the original design, the repositories should be created in the us-east-1 region. One repository is for the application, intended for software developers, and the other repository is for infrastructure, intended for devops. 1.1: AWS Management Console, set the us-east-1 region [this is per the design document] 1.2: AWS Management Console, search for CodeCommit, click CodeCommit 1.3: Create repository 1.4: Set Repository name and description, Create 1.5: Repository was created successfully 1.6: Click on

This post is part of a 5-post series on using Git. Hands-on Git Tasks - Part #1 of 5 | First Git Commit Hands-on Git Taks - Part #2 of 5 | Checking Git Objects Hands-on Git Tasks - Part #3 of 5 | Navigating Project Branches Hands-on Git Tasks - Part #4 of 5 | Using Remote Repository Hands-On Git Tasks - Part #5 of 5 | Merging Follow these steps for an example of how to merge code from a 'feature' branch into the 'main' branch. Did glance over branching in an earlier tutorial, but did not cover the merging of branches. 01. Go to the local-repo folder 02. check branches: git branch 03. create a new branch: git branch feature 04. check branches again: git branch 05. checkout the feature branch 06. create, add and commit a new file in 'switching' branch: switching.txt ls echo "circuit, packet, message" > switching.txt git add switching.txt git commit -m "Added switching feature" ls 07. get-back to the '

This post is part of a 5-post series on using Git. Hands-on Git Tasks - Part #1 of 5 | First Git Commit Hands-on Git Taks - Part #2 of 5 | Checking Git Objects Hands-on Git Tasks - Part #3 of 5 | Navigating Project Branches Hands-on Git Tasks - Part #4 of 5 | Using Remote Repository Hands-On Git Tasks - Part #5 of 5 | Merging Follow these steps for an example of how to work with a remote repository using your AWS Cloud9 Environment. (For steps to create your Cloud9 Environment, go here: https://medium.com/@lewislampkin/creating-an-integrated-developer-environment-ide-in-the-cloud-in-two-minutes-c96e33b2fa3e ) (This example assumes you have a Github account. If not, create one here: https://github.com/signup? ) (This example assumes you setup a personal access token for GitHub [in lieu of password]. If not, create one here: https://docs.github.com/en/enterprise-server@3.8/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens ) 01. O