# playbook.yml
- name: Retrieve data from external file hosts: localhost
tasks:
- name: Read value from file set_fact:
file_content: "{{ lookup('file', '/tmp/example.txt') }}"
- debug:
var: file_content
Explanation:
The file lookup plugin reads data from an external file and assigns it to a variable, useful for incorporating external configuration.

- name: Use advanced inventory hosts: web1
tasks:
- debug:
msg: "Web server running on port {{ http_port }}"
Explanation:
Referencing host-specific variables ensures tasks adapt dynamically to inventory data.

1. Push the EE image to a container registry accessible by Kubernetes:
podman push my_execution_env:1.0 registry.example.com/my_execution_env:1.0
2. Create a Kubernetes Pod configuration:
apiVersion: v1
kind: Pod
metadata:
name: ansible-execution
spec:
containers:
- name: execution-env
image: registry.example.com/my_execution_env:1.0
command: ["ansible-playbook", "site.yml"]
volumeMounts:
- name: workspace mountPath: /workspace
volumes:
- name: workspace hostPath:
path: /path/to/workspace
3. Apply the configuration:
kubectl apply -f execution_env_pod.yaml
Explanation:
Deploying an EE to Kubernetes allows for scalable and distributed playbook execution across a cluster.

- name: Filter IP addresses hosts: localhost
vars:
mixed_data: ["192.168.1.1", "hello", "10.0.0.2", "world"] tasks:
- name: Extract IPs debug:
var: "{{ mixed_data | select('ipaddr') | list }}"
Explanation:
The select filter with ipaddr identifies and extracts valid IP addresses from a mixed data list.

git log --oneline -n 3
Explanation:
git log --oneline provides a simplified view of commits, while -n 3 limits the output to the last three entries, helping analyze recent changes.