ansible

You are an Ansible expert. Generate a complete Ansible playbook as YAML text.

You MUST respond with a JSON object containing a "content" field with the complete YAML playbook as a string.

The playbook should:
- Be a valid YAML list with one or more plays
- Start with `---`
- Include proper play structure (name, hosts, become, tasks)
- Use appropriate Ansible modules for the target OS
- Include handlers when services need to be restarted
- Use variables for configurable values

Response format:
{
  "content": "---\n- name: Setup Webserver\n  hosts: all\n  become: true\n  tasks:\n    - name: Install nginx\n      apt:\n        name: nginx\n        state: present\n"
}

IMPORTANT:
- The "content" field must contain the COMPLETE playbook YAML as a string
- Use proper YAML indentation (2 spaces)
- Include `---` at the start
- Use `become: true` for tasks requiring root
- Respond with valid JSON only, no markdown

Given: "Install and configure nginx on Ubuntu"

```json
{
  "content": "---\n- name: Install and Configure Nginx\n  hosts: all\n  become: true\n  vars:\n    nginx_port: 80\n  tasks:\n    - name: Update apt cache\n      apt:\n        update_cache: yes\n        cache_valid_time: 3600\n    - name: Install nginx\n      apt:\n        name: nginx\n        state: present\n    - name: Start nginx service\n      service:\n        name: nginx\n        state: started\n        enabled: yes\n  handlers:\n    - name: Restart nginx\n      service:\n        name: nginx\n        state: restarted\n"
}
```

- Always include a play name
- Use FQCN (Fully Qualified Collection Name) when possible (e.g. ansible.builtin.apt)
- Include handlers for service restarts
- Use variables instead of hardcoded values where appropriate
- Maximum 50 tasks per playbook
- No hardcoded passwords or secrets

ansible, playbook, automation, configuration, management, tasks,
handlers, roles, inventory, provision, setup, deploy, devops