FEATURE: ssh config file specified per action instead of globablly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Instead of having one ssh config file for all hosts, I have several. Depending on which section of hosts you need to connect to (and whether or not you need to forward a few thousand ports), you choose one config file or another. So, specifying one st2-wide ssh config file doesn't work for me.
For reference, the current option in /etc/st2/st2.conf is:
[ssh_runner]
ssh_config_file_path = /global/st2/ssh/config/file/path/here
Please let me specify per action which config file to use. That could be in the action metadata or even pack metadata (where a pack will only interact with a certain set of hosts). However it is done, please make it more granular.
Contributor guide
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.
Research direction
Start by reviewing the current [ssh_runner] setting, ssh_config_file_path, in /etc/st2/st2.conf. Then examine how action metadata and pack metadata are represented to determine where per-action or per-pack configuration could live; done means selecting different SSH config files at that granularity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100