sho/homelab-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix bash formatting

Browse Source
This commit is contained in:
Isshi0417 2026-07-03 01:58:49 +00:00
parent 40e615968a
commit e14d796e47
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/03_ansible_automation.md
View File

@ -43,9 +43,9 @@ For security, I cannot commit plain-text credentials (like Red Hat Customer Port
I created an external variables file vault.yml containing my sensitive data and encrypted it using **Ansible Vault:**
```bash
```bash
ansible-vault encrypt vault.yml
```
```
* **Encryption Standard:** Ansible Vault uses AES-256 encryption.
* **Decryption:** The file is completely scrambled on disk. When playbooks are executed, `--ask-vault-pass` flag can be passed. Ansible prompts for the master password, decrypts the variables directly in memory, runs the tasks, and discards the plaintext variables immediately when finished.
@ -64,9 +64,9 @@ Because I am already runnin ginside a Dev Container, trying to launch another co
I disabled the nested execution environment flag using `--ee false`:
```bash
```bash
ansible-navigator run configure_nodes.yml --mode stdout --ee false
```
```
* **--ee false:** Forces ansible-navigator to run playbooks directly inside the current Dev Container shell, using the pre-installed tools and collections, bypassing the nested container layer.
* **--mode stdout:** Standardizes the console output to log directly to the terminal line-by-line, matching the traditional ansible-playbook output format.