メニュー
Ansible operations patterns covering playbook execution, secret management with 1Password, task automation, and security best practices. Use when writing or running Ansible playbooks.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/code0100fun/botfiles --skill ansible-opsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Guide for using bees, a local-first issue tracker (SQLite DB + a committed issues.jsonl) driven by the `bees` CLI. Use for ALL task/issue tracking on bees projects — creating issues, organizing them into epics with dependencies, the in_progress→closed lifecycle, and syncing/committing the tracker.
Guide for creating well-structured conventional commits. Use when creating git commits, drafting commit messages, or reviewing commit message quality.
My personal cross-codebase development workflow — set up tooling with mise, track work in Bees, make focused changes, commit with the commit-message-guide conventions, and land the plane cleanly. Use when starting or running a development task on a project that follows this workflow (mise + Bees + Git).
SKILL.md を表示中
SOC 職業分類に基づく
| name | ansible-ops |
| description | Ansible operations patterns covering playbook execution, secret management with 1Password, task automation, and security best practices. Use when writing or running Ansible playbooks. |
Use a task runner (like mise, make, or just) to wrap playbook execution and handle environment setup:
# Preferred: Use task runner that loads env automatically
mise run playbook ansible/playbooks/deploy-service-stack.yml
# With extra ansible-playbook arguments
mise run playbook ansible/playbooks/deploy-monitoring-stack.yml --ask-become-pass
# Direct execution (ensure env vars are loaded first)
ansible-playbook -i ansible/inventory/hosts.ini ansible/playbooks/deploy-service.yml
Store the 1Password service account token in a .env file (gitignored) and load it automatically through your task runner:
# .env (NEVER commit this)
OP_SERVICE_ACCOUNT_TOKEN=ops_xxxxx...
# Verify authentication
op whoami
# Should show: User Type: SERVICE_ACCOUNT
- name: Deploy service with secrets
environment:
API_KEY: "{{ lookup('env', 'OP_SERVICE_ACCOUNT_TOKEN') | community.general.onepassword_raw('API Key', vault='MyVault') }}"
Important notes:
community.general.onepassword lookup may not support service accounts directlyop CLI directly in playbooks with the environment token.env file must be in .gitignore - NEVER commit itno_log: true in Ansible tasks that handle secrets:- name: Set secret environment variable
ansible.builtin.lineinfile:
path: /etc/environment
line: "SECRET_KEY={{ secret_value }}"
no_log: true
- name: Deploy web service
hosts: web_servers
become: true
tasks:
# 1. Create required directories
- name: Ensure config directory exists
ansible.builtin.file:
path: /opt/myservice/config
state: directory
owner: appuser
group: appgroup
mode: "0755"
# 2. Deploy configuration files
- name: Copy service configuration
ansible.builtin.template:
src: templates/service.conf.j2
dest: /opt/myservice/config/service.conf
owner: appuser
group: appgroup
mode: "0644"
notify: restart service
# 3. Deploy the service
- name: Deploy docker stack
community.docker.docker_stack:
name: myservice
compose:
- /opt/myservice/docker-compose.yml
Every task should be safe to run multiple times:
# GOOD: Idempotent - creates only if missing
- name: Create data directory
ansible.builtin.file:
path: /data/myservice
state: directory
mode: "0755"
# BAD: Not idempotent - appends every run
- name: Add config line
ansible.builtin.shell: echo "setting=value" >> /etc/config
Always set permissions explicitly:
- name: Deploy config file
ansible.builtin.copy:
src: files/config.yaml
dest: /opt/service/config.yaml
owner: appuser
group: appgroup
mode: "0644" # Always set mode explicitly
Use handlers for service restarts:
handlers:
- name: restart service
community.docker.docker_stack:
name: myservice
compose:
- /opt/myservice/docker-compose.yml
state: present
- name: reload nginx
ansible.builtin.service:
name: nginx
state: reloaded
# ansible/inventory/hosts.ini
[web_servers]
web-01 ansible_host=10.0.0.10
web-02 ansible_host=10.0.0.11
[db_servers]
db-01 ansible_host=10.0.0.20
[gpu_nodes]
gpu-01 ansible_host=10.0.0.30
[all:vars]
ansible_user=deploy
ansible_become=true
- name: Deploy compose file
ansible.builtin.copy:
src: "{{ playbook_dir }}/../docker/stacks/myservice/docker-compose.yml"
dest: /opt/myservice/docker-compose.yml
mode: "0644"
- name: Deploy templated config
ansible.builtin.template:
src: templates/config.yml.j2
dest: /opt/service/config.yml
mode: "0644"
vars:
db_host: "{{ hostvars['db-01'].ansible_host }}"
app_port: 8080
- name: Wait for service to be healthy
ansible.builtin.uri:
url: "http://localhost:8080/health"
status_code: 200
register: result
until: result.status == 200
retries: 30
delay: 5
# Dry run (check mode)
ansible-playbook playbook.yml --check
# Verbose output
ansible-playbook playbook.yml -vvv
# Limit to specific hosts
ansible-playbook playbook.yml --limit web-01
# List tasks without executing
ansible-playbook playbook.yml --list-tasks
# Start at a specific task
ansible-playbook playbook.yml --start-at-task="Deploy config"