Feature request: Ansible Connection Plugin
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ansible, python
- Domain
- devops, networking
Research direction
Start with the linked Ansible connection-plugin development guide and inspect the repository for existing Ansible or client integration points; no files or tests are named in the issue. Define the plugin's inputs around the pidgeons connection type, iroh ID, and authentication, then verify that it supports multiple managed hosts and the documented switch from ssh.
Written by the indexing model from the issue text.
Description
Ansible Connection plugins (docs here) are how Ansible abstracts away the implementation details of how traffic flows from the Control node(s) to the Managed node(s). While ansible comes with several, and defaults to ssh, it is modular in nature and allows for 3rd parties to extend the list when their plugins are installed (typically through ansible galaxy).
Developers of Ansible Playbooks describe the list of Managed nodes in a host list, often in INI or YAML format, and as part of that description, they describe how the Ansible Control node may connect to each Managed node. This is typically done by specifying the connection plugin to use (ansible comes with several pre-installed, and defaults to ssh), and arguments to that connection plugin, such as the IP address, port and username.
In the case of a pigeons-based Ansible Connection plugin, the ideal data that would be provided to Ansible would be that the connection plugin to be used is pidgeons, the iroh ID, and any authentication information.
It is my assumption that the ideal way to implement this would to follow their guide on how to make such a plugin. Plugins are typically written in python, and this plugin should make a few assumptions:
- We are connecting as a client to multiple different hosts, all at the same time, using pidgeons.
- The pidgeons servers on the Managed nodes are fully configured and running already.
- a pidgeons and a ssh client are both installed on the Control node
- For a user to switch from
sshtopidgeons, all they would need to do is- change the connection type
- install a pidgeons client
- install the Ansible Connection plugin
- replace the IP or DNS address that the ssh client would have discovered the Managed node by with the iroh address. (
ansible_host)
- Dominant language
- Rust
- Stars
- 207
- Forks
- 9
- Avg merge
- 12h 25m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from n0-computer/pigeons
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
n0-computer/pigeons#27 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
n0-computer/pigeons#25 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
n0-computer/pigeons#24 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
n0-computer/pigeons#20 · 3 reactions ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
n0-computer/pigeons#13 ·
All issues in n0-computer/pigeons
Similar issues
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
sims1253/r-typeshed#140 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/craft-libs#2867 ·
Maintainers usually reply within 1 day
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100