SVIG/python-bootcamp
7
0
Fork 1
Code Issues Pull Requests 1 Releases Wiki Activity

Update page '6-12-2023 Cohort 1 Sync Notes'

j
2023-06-13 02:04:21 +02:00
parent 05f6b1a295
commit 8b6b218e71
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
6-12-2023 Cohort 1 Sync Notes.md
+3
@@ -34,12 +34,15 @@ Ansible magic variables: https://docs.ansible.com/ansible/latest/reference_appen
* Explained that `become: true` gives extra privileges to the tasks that run under that play/task, and make sure to stop using it once you're done using administrative ansible modules and can go back to being a regular user. * Explained that `become: true` gives extra privileges to the tasks that run under that play/task, and make sure to stop using it once you're done using administrative ansible modules and can go back to being a regular user.
* You can use block to group tasks by a `when` condition or a `become` command * You can use block to group tasks by a `when` condition or a `become` command
* How to dump ansible variables in a playbook: * How to dump ansible variables in a playbook:
``` ```
... tasks above here ... tasks above here
register: pricer_container register: pricer_container
- error: - error:
msg: "{{ pricer_container }}" msg: "{{ pricer_container }}"
``` ```
* All tasks return some values: https://docs.ansible.com/ansible/2.9/reference_appendices/common_return_values.html#common-return-values * All tasks return some values: https://docs.ansible.com/ansible/2.9/reference_appendices/common_return_values.html#common-return-values
* docker_container returns some information about the container: https://docs.ansible.com/ansible/2.9/modules/docker_container_module.html#return-values * docker_container returns some information about the container: https://docs.ansible.com/ansible/2.9/modules/docker_container_module.html#return-values
* Next step is to figure out how to extract the container name so we can use it later to stop and re-start the container with systemd, then do it again once selenium is installed * Next step is to figure out how to extract the container name so we can use it later to stop and re-start the container with systemd, then do it again once selenium is installed
1704h: ended