mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 20:26:33 +00:00
evangelostsak
9accaee134
Ansible appends -tt to any task it cannot pipeline when the task escalates, and ansible.builtin.script is one of those, so the deploy over the mesh ran those tasks on a pty. A pty ends every line with a carriage return, while the container connection this transport replaces returned bare newlines. A role that reads its own stdout therefore started failing for no reason other than the deploy having moved onto the mesh: the Matomo bootstrap parsed a perfectly good token as empty, because its regex anchors each line and a trailing carriage return defeats that anchor. The host the tool switches now asks for no tty, so the mesh returns the same bytes the connection it replaced did, and no role has to learn about the transport underneath it. Taken from the connection plugin rather than guessed: the tty is added when the task cannot pipeline and escalates, and the option carrying it is exposed per host as ansible_ssh_use_tty.
Administration 🛠️
Operator-facing tooling for provisioning inventories, running dedicated deploys, and managing host secrets across an Infinito.Nexus environment.