Clone with a Difference⚓︎
Direct link: Intro terminal
Clone a code repository. Get hints for this challenge from Bow Ninecandle in the Elfen Ring.
Well hello! I'm Bow Ninecandle!
Have you ever used Git before? It's so neat!
It adds so much convenience to DevOps, like those times when a new person joins the team.
They can just clone the project, and start helping out right away!
Speaking of, maybe you could help me out with cloning this repo?
I've heard there's multiple methods, but I only know how to do one.
If you need more help, check out the panel of very senior DevOps experts.
HTTPS Git Cloning
There's a consistent format for Github repositories cloned via HTTPS. Try converting!
We just need you to clone one repo: 'git email@example.com:asnowball/aws_scripts.git' This should be easy, right? Thing is: it doesn't seem to be working for me. This is a 'public' repository though. I'm so confused! Please clone the repo and 'cat' the 'README.md' file. Then 'runtoanswer' and tell us the last word of the README.md file!
Some of the challenges are designed to help you get acquainted with a specific technology or tool. In previous years, hint terminals were separate from the main objectives. This year however, for the first time, they're much more integrated into the main storyline. For this objective, we need to familiarize ourselves with Git, in preparation for the Jolly CI/CD objective.
Trying to clone the repository using
git clone firstname.lastname@example.org:asnowball/aws_scripts.git will throw an error stating Permission denied (publickey), indicating our SSH key located at
/home/bow/.ssh/id_rsa isn't accepted. Since Bow notes that this is a public repository, we don't really need to clone via SSH and we should be able to use HTTPS instead.
Using the hint and rewriting the Git URL as https://haugfactory.com/asnowball/aws_scripts.git allows us to successfully clone the repository using
git clone https://haugfactory.com/asnowball/aws_scripts.git. We can also verify that the URL has been correctly converted by opening it in a web browser, which will bring up a GitLab web interface for the repository.
cd into the
aws_scripts folder, find the last word in the
README.md file, and submit it using
Wow - great work! Thank you!
Say, if you happen to be testing containers for security, there are some things you should think about.
Developers love to give ALL TeH PERMz so that things "just work," but it can cause real problems.
It's always smart to check for excessive user and container permissions.
You never know! You might be able to interact with host processes or filesystems!