- name: Execute as admin user hosts: all
tasks:
- name: List files
become: yes
become_user: admin
command: ls /home/admin
Explanation:
The become_user directive specifies which user to act as during a privileged task, useful for user-specific configurations or actions.

- name: Store control node result hosts: web1
tasks:
- name: Get disk usage on control node
command: df -h
delegate_to: localhost
register: disk_usage
- name: Show disk usage debug:
var: disk_usage
Explanation:
This task demonstrates delegating commands to the control node while retaining results within the managed host's context.

mkdir -p my_namespace/my_collection/tests
echo "---
# Test cases" > my_namespace/my_collection/tests/test.yml
Explanation:
Adding a test directory ensures the collection can be validated through automated test cases.

1. Navigate to Credentials and add: o Type: Source Control
o Username: Leave blank
o SSH Private Key: Upload your private key.
2. Create a project:
o Source Control Type: Git
o URL: [email protected]:private/repo.git
o Credential: Select the SSH credential.
3. Sync the project.
Explanation:
Using an SSH key allows secure access to private repositories for pulling automation content.

1. Add Container Registry credentials: o Registry URL: registry.example.com o Username and password.
2. Add the EE:
o Name: Private EE
o Image: registry.example.com/my_execution_env:latest
3. Use this EE in a job template.
Explanation:
Pulling EEs from private registries ensures secure and controlled access to customized runtime environments.