ansible-collections/silvarion.provision
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Wire proxmox_ssh_automation_key into the container (sysadmin) connection too #11

Merged
sysadmin merged 1 commit from fix/sysadmin-automation-key into main 2026-10-06 20:22:26 +00:00
Conversation 0 Commits 1 Files changed 6 +87 -3
sysadmin commented 2026-10-06 20:15:34 +00:00
Contributor
Copy link

Step 6's connection setup for Play 3 already read proxmox_ssh_private_key_file to set ansible_ssh_private_key_file on the created container, but nothing ever set that var -- Play 3 fell back to ambient SSH identity, the same class of gap already fixed for the Proxmox-host connection (PR #5), just one layer further out.

proxmox_ssh_private_key_file now points at the same key file already written for the Proxmox-host connection. New proxmox_ssh_automation_key_pub is pushed into every newly-created container's sysadmin authorized_keys alongside proxmox_ssh_sysadmin_key (not replaced).

Verified live: confirmed the automation key authenticates to an existing container with SSH agent fallback disabled.

🤖 Generated with Claude Code

https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp

Step 6's connection setup for Play 3 already read proxmox_ssh_private_key_file to set ansible_ssh_private_key_file on the created container, but nothing ever set that var -- Play 3 fell back to ambient SSH identity, the same class of gap already fixed for the Proxmox-host connection (PR #5), just one layer further out. proxmox_ssh_private_key_file now points at the same key file already written for the Proxmox-host connection. New proxmox_ssh_automation_key_pub is pushed into every newly-created container's sysadmin authorized_keys alongside proxmox_ssh_sysadmin_key (not replaced). Verified live: confirmed the automation key authenticates to an existing container with SSH agent fallback disabled. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp
Wire proxmox_ssh_automation_key into the container (sysadmin) connection too
All checks were successful
Ansible Lint / ansible-lint (pull_request) Successful in 1m19s
Details
2f5961e160 
Step 6's connection setup for Play 3 (create/lxc.yml, "write host_vars
file for tech play") already read proxmox_ssh_private_key_file to set
ansible_ssh_private_key_file on the created container, but nothing ever
set that var -- Play 3 fell back to ambient SSH identity, the same class
of gap already fixed for the Proxmox-host connection (PR #5), just one
layer further out. Confirmed live as a plain "Permission denied"
connecting as sysadmin to an already-existing container.

proxmox_ssh_private_key_file now points at the same key file already
written for the Proxmox-host connection. New
proxmox_ssh_automation_key_pub (public half) is pushed into every
newly-created container's sysadmin authorized_keys alongside
proxmox_ssh_sysadmin_key (the operator's own personal key, not replaced)
-- without it, a freshly-created container has no automation identity
to connect with in the first place.

Verified live: generated the keypair's public half, confirmed it
authenticates to an existing container with SSH agent fallback disabled.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ansible-collections/silvarion.provision!11
No description provided.