Skip to content

Commit 9793a07

Browse files
committed
chore: playbook 1 - minor semantics, playbook 2 - ssh pw note added
1 parent ffe7f9a commit 9793a07

2 files changed

Lines changed: 7 additions & 3 deletions

File tree

_partials/ubuntu_ansible_part1.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ cd ~/vm-ansible-setup && ansible-playbook playbooks/setup_vm_part1.yml
4646

4747
And the playbook should start running!
4848

49-
❗ If an errors occur, raise a ticket with a teacher. The ansible playbooks are designed so that they can be run again, and again, and again and only make the changes that are required.
49+
❗ If an errors occur, raise a ticket with a teacher. The ansible playbooks are designed so that they can be run again, and again, and again and only make the changes that are required (a cool concept called _Idempotency_ that you'll learn about later 😉).
5050

5151
### What is the playbook installing?
5252

@@ -63,4 +63,4 @@ While this playbook is running, lets go through what is being installed and conf
6363

6464
The playbook is also running checks to see if things are installed or not. This is so you can safely re-run the playbook without any problems.
6565

66-
💡 Curious about how Ansible playbooks are defined, take a look at the playbook being run at this [link here 🔗](https://github.com/lewagon/data-engineering-setup/blob/main-automation/automation/vm-ansible-setup/playbooks/setup_vm_part1.yml)
66+
💡 Curious about how Ansible playbooks are defined, take a look at the playbooks' source code at this [link here 🔗](https://github.com/lewagon/data-engineering-setup/blob/main-automation/automation/vm-ansible-setup/playbooks/setup_vm_part1.yml). You might not understand exactly what is happening, but should be able to identify the different tasks.

_partials/ubuntu_ansible_part2.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,11 @@ cd ~/vm-ansible-setup && ansible-playbook playbooks/setup_vm_part2.yml
2020

2121
And the playbook should start running! If you're asked if you want VS Code to behave more like Sublime Text, click accept.
2222

23-
❗ If any errors occur, raise a ticket with a teacher. You can safely run the playbook again.
23+
**If you created a password for your GitHub SSH key**
24+
- You may asked to type it in your password when the during the playbook run
25+
- The task: **Clone data-engineering-challenges from your GitHub to VM** will fail. This is OK and expected with how SSH keys work and how the playbooks are modifying your configuration. To resolve, in your terminal run: `exec zsh`, and then re-run the playbook.
26+
27+
❗ If any other errors occur, or your are unsure, raise a ticket with a teacher. You can safely run the playbook again and again. Generally, if the playbook runs from start to finish with no errors, everything should be good!
2428

2529
### What is the playbook installing?
2630

0 commit comments

Comments
 (0)