mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 07:06:00 +03:00
[GH-ISSUE #66] What privileges necessary? #36
Labels
No labels
backend:https
backend:local
backend:openssh
backend:ssh_paramiko
pull-request
status:ansible-issue
status:help-wanted
status:info-needed
status:proxmox-issue
status:review-needed
type:bug 🐞
type:dependency ⛓️
type:docs 📝
type:enhancement ⏫
type:maintenance 🛠️
type:meta
type:question ❓
type:request ✋
type:testing 🧪
version:1.x
version:latest
version:py2
version:py3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmoxer#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FuzzyMistborn on GitHub (Sep 21, 2021).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/66
I'm looking to lock down access to my Proxmox server and am using Ansible to create VMs/LXCs. Currently I'm using an API token and with the PVEAdmin role but I'm wondering if I can reduce that still further. From playing around a bit it looks like I need a cross between the PVEDatastoreAdmin and PVEVMAdmin roles (https://pve.proxmox.com/wiki/User_Management#pveum_permission_management). Just trying to get a sense of what privileges are specifically required. This may not be the right place to ask (may need to go to ansible) so you can tell me to go there and I won't be offended :-)
@jhollowe commented on GitHub (Sep 21, 2021):
Unless someone else can give an exact answer, the best I can say is to look at the Ansible code, what API calls it is making, and see in the PVE API documentation what permissions are needed for each. Each endpoint in the API docs should tell you the permission needed and the path it is needed on. I would start with no permissions and add the needed ones until Ansible does what you want. Being able to create LXC containers will obviously be greater permissions than just reading state from PVE, but the Home Assistant PVE integration only needs Auditor role.
I would also suggest creating a role for ansible in PVE rather than setting all the permissions on the API Token itself so you can easily revoke it or create additional tokens without having to reinvent the wheel with your permissions.
@FuzzyMistborn commented on GitHub (Sep 22, 2021):
Thanks, I'll take a look. Appreciate it!