connection plugin
The plugin that decides how Ansible reaches a host: SSH by default, or local, WinRM, a container runtime or a network device protocol.
In more detail
Which one is used is just a variable, ansible_connection, so it can be set per host or per group. SSH is right almost every time; local runs on the control node; WinRM or PowerShell remoting suits Windows; there are plugins for containers and for network devices that offer only a command line.
Related terms
- local connection — The connection plugin that runs modules directly on the control node, with no SSH and no network at all.
- SSH — A protocol for logging in to and running commands on another computer securely over a network.
- WinRM — Windows Remote Management, Microsoft's protocol for running commands on Windows machines over the network, which Ansible uses instead of SSH.
- connection variables — Inventory variables with reserved names, such as ansible_user, ansible_port and ansible_connection, that tell Ansible how to reach and log in to a host.
- plugin — An add-on package that extends a tool with extra features without changing the tool itself.
Taught in
- Connections And Privilege Escalation — Ansible Configuration Management at Scale
- Playbook Syntax And YAML — Ansible Configuration Management at Scale
- Writing Your First Playbook — Ansible Configuration Management at Scale
- Modules And Idempotency — Ansible Configuration Management at Scale
- Check Mode And Diff — Ansible Configuration Management at Scale
- Handlers And Notify — Ansible Configuration Management at Scale
- Variables And Precedence — Ansible Configuration Management at Scale
- Gathering Facts — Ansible Configuration Management at Scale
- Conditionals — Ansible Configuration Management at Scale
- Loops — Ansible Configuration Management at Scale
- Templates With Jinja — Ansible Configuration Management at Scale
- Error Handling With Block, Rescue And Always — Ansible Configuration Management at Scale
- Writing A Role — Ansible Configuration Management at Scale