[GH-ISSUE #76] Add support for local #42

Closed
opened 2026-02-27 15:46:08 +03:00 by kerem · 7 comments
Owner

Originally created by @McTwist on GitHub (Nov 24, 2021).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/76

Originally assigned to: @jhollowe on GitHub.

Currently you are required to access a node "remotely" through its name. But if for some reason you want to run locally and do not want to use any type of authentication, this falls flat.

I would recommend to add a service for local, where it will do exactly like ssh, but using Popen instead for local access.

Originally created by @McTwist on GitHub (Nov 24, 2021). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/76 Originally assigned to: @jhollowe on GitHub. Currently you are required to access a node "remotely" through its name. But if for some reason you want to run locally and do not want to use any type of authentication, this falls flat. I would recommend to add a service for local, where it will do exactly like ssh, but using `Popen` instead for local access.
kerem 2026-02-27 15:46:08 +03:00
Author
Owner

@jhollowe commented on GitHub (Nov 24, 2021):

you can use one of the SSH backends and use "localhost" as the host if you are running Proxmoxer on a PVE/PMG/PBS node.

<!-- gh-comment-id:978067282 --> @jhollowe commented on GitHub (Nov 24, 2021): you can use one of the SSH backends and use "localhost" as the host if you are running Proxmoxer on a PVE/PMG/PBS node.
Author
Owner

@reitermarkus commented on GitHub (Jan 12, 2022):

Could a dedicated local backend be added? In my case at least, ssh root@localhost gets stuck since localhost is not in known_hosts, and I also don't think it should be.

<!-- gh-comment-id:1010771906 --> @reitermarkus commented on GitHub (Jan 12, 2022): Could a dedicated `local` backend be added? In my case at least, `ssh root@localhost` gets stuck since `localhost` is not in `known_hosts`, and I also don't think it should be.
Author
Owner

@McTwist commented on GitHub (Jan 12, 2022):

#77 has already been declined, but please do voice your opinion about this to increase the need for it.

<!-- gh-comment-id:1011000152 --> @McTwist commented on GitHub (Jan 12, 2022): #77 has already been declined, but please do voice your opinion about this to increase the need for it.
Author
Owner

@reitermarkus commented on GitHub (Jan 12, 2022):

This would be very beneficial for use in the Proxmox Ansible module which uses this library. Ansible already ssh's to a given node itself, so this would alleviate the need for depending on another SSH library and reduce boilerplate in playbooks quite a lot.

<!-- gh-comment-id:1011121317 --> @reitermarkus commented on GitHub (Jan 12, 2022): This would be very beneficial for use in the Proxmox Ansible module which uses this library. Ansible already ssh's to a given node itself, so this would alleviate the need for depending on another SSH library and reduce boilerplate in playbooks quite a lot.
Author
Owner

@jhollowe commented on GitHub (Jan 12, 2022):

Ah, yeah that makes sense. I was wondering the utility of local/cli access, but when using Ansible you are already SSHed into the host and running in Python. A single dependency on proxmoxer vs proxmoxer+(openssh|paramiko) is obviously preferred in this setup as well. And the fact that all you need is the SSH access for Ansible and wouldn't need any other creds once connected.

There are some other features I would like to get implemented and released first, but I would be willing to add a local backend in the following release. And yes, there needs to be some refactoring done to reduce duplicate code between SSH and local, but that should be easy.

<!-- gh-comment-id:1011493420 --> @jhollowe commented on GitHub (Jan 12, 2022): Ah, yeah that makes sense. I was wondering the utility of local/cli access, but when using Ansible you are already SSHed into the host and running in Python. A single dependency on proxmoxer vs proxmoxer+(openssh|paramiko) is obviously preferred in this setup as well. And the fact that all you need is the SSH access for Ansible and wouldn't need any other creds once connected. There are some other features I would like to get implemented and released first, but I would be willing to add a local backend in the following release. And yes, there needs to be some refactoring done to reduce duplicate code between SSH and local, but that should be easy.
Author
Owner

@jhollowe commented on GitHub (Jan 12, 2022):

Backend name ideas?

👍 for local
🚀 for cli
comment below for other ideas

<!-- gh-comment-id:1011494189 --> @jhollowe commented on GitHub (Jan 12, 2022): Backend name ideas? 👍 for `local` 🚀 for `cli` comment below for other ideas
Author
Owner

@McTwist commented on GitHub (Jan 13, 2022):

Will #77 be used, or will you create your own?

<!-- gh-comment-id:1011948943 --> @McTwist commented on GitHub (Jan 13, 2022): Will #77 be used, or will you create your own?
Sign in to join this conversation.
No milestone
No project
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
starred/proxmoxer#42
No description provided.