메뉴
Verify or refresh the OpenTofu-to-Ansible inventory distribution (RustFS-published; apply is the publish boundary)
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | sync-inventory |
| description | Verify or refresh the OpenTofu-to-Ansible inventory distribution (RustFS-published; apply is the publish boundary) |
The inventory pipeline is automatic: every successful tofu-proxmox
Terrakube apply validates ansible_inventory in the OpenTofu graph and
publishes it to the homelab RustFS object store with aws_s3_object. There is
no post-apply hook or manual mirror step.
Consumers (ansible-proxmox, ansible-proxmox-apps, ansible-splunk) resolve
identically via their load_tofu.yml:
TOFU_INVENTORY_PATH — explicit pin (tests/overrides)amazon.aws fetch over the homelab network;
scoped credentials come from OpenBao, with no IaC checkout or toolchainThere is no manual export/transform/copy flow. Never run
tofu output -json ansible_inventory > <consumer>/inventory/... by hand —
hand-injected inventories bypass the schema gate and create unmanaged drift.
aws s3api head-object \
--endpoint-url "$RUSTFS_ENDPOINT" \
--bucket "$TOFU_INVENTORY_BUCKET" \
--key "$TOFU_INVENTORY_KEY" \
--query LastModified
If it predates the last intended infrastructure change, the publish boundary
was not crossed — run a real apply (next step). Reference docs:
tofu-proxmox/docs/INVENTORY_PUBLISHING.md.
The only way to republish is the publish boundary itself:
cd $GIT_HOME_PUBLIC/homelab/tofu-proxmox/main
tofu apply
The command submits a remote Terrakube run. The workspace lock serializes changes, Terrakube obtains its OpenBao credentials natively, and the apply updates the RustFS object only when content changed.
In any consumer repo (no creds needed if the cache exists):
ansible-playbook <load_tofu path> -i inventory/hosts.yml -c local
playbooks/load_tofu.ymlinventory/load_tofu.ymlWatch which resolution step wins ("Resolve inventory from …" task output).
TOFU_INVENTORY_PATH to a known-good
copy, or run the apply.Use when creating PRs, linking issues, managing PR comments, or creating GitHub issues
Use when creating or editing GitHub Actions workflows that call reusable workflows (uses: OWNER/repo/.github/workflows/...) — org owner references must be the literal current org, and shared-CI homes are under dryvist.
Emit a paste-ready two-part handoff for a fresh session: a `## Goal statement` hard-capped under 4000 characters (measured with wc -c, never estimated) that pastes straight into Claude Code's /goal Stop hook, plus an unbounded `## Full prompt` carrying cwd, ordered reading list, hard rules, pitfalls, and deliverables. Use when forking work to a new session, spinning up an orchestrator, or when wrap-up needs a next-session prompt with a real goal and not just a task list.
Analyzes current session state and repository status without any cleanup. Full mode (default): resolves the active plan file, reads plan checklist + TaskList, gathers unfinished work/issues from conversation history, checks git status, and emits a /handoff-built next-session prompt. Mid-session mode (`/session-status mid`): a fast plain-language 'done vs remaining' snapshot for mid-flight orientation, skipping the history scan, triage, and handoff.
End-of-session handler that first checks whether the current session's plan is actually complete. If complete: refresh repo, run quick retrospective, clean gone branches, and emit a forward-looking follow-up prompt. If incomplete: skip cleanup and emit one or more `cd`-into-worktree blocks paired with ready-to-paste resume prompts so the unfinished work can be picked up cold in a new session.
Automatically finalize pull requests for merge by resolving CodeQL violations, review threads, merge conflicts, and CI failures. Handles single PR (current branch or by number), all open PRs in the repo, or all open PRs across the org. Includes bot-authored PRs in all modes.