Search results

I have found a satisfactory solution. I use the pvesh command for API access via SSH. Now the restricted user jenkins can execute the command pvesh without PW via SSH. I have shell wrapper scripts written to manage the VMs. To access the JSON objects in shell scripts, the program jq is very...

Thanks, I'll check.

Thanks for the note. This is currently still no problem, because currently there is only one node. But this may change in the future. But certainly one more reason to use the API.

Thanks Aleksandrs, that's a good indication - per se. But, unfortunately, that will not solve my other problem with the CLI. Therefore, it makes sense to follow Dietmar's recommendation and instead use the API. It probably makes sense to write an API wrapper for scripting, but something is...

OK, this makes the CLI unsuitable for my application. It probably makes sense to write an API wrapper for scripting. Thanks for the quick reply.

Thank you Aleksandrs for the good hint. That's worth a try. Unfortunately, this probably will not solve my other problem with CLI. Therefore, it is better to follow Dietmar's probably recommendation and use the API instead of the CLI. It probably makes sense to write an API wrapper for...

I have a question about a product feature. There are non-root restrictions on the execution rights of the Proxmox CLI? I have found nothing in this regard in the wiki or iNet. I've added an additional user 'jenkins' for automation, written in the WIKI. This remote login should not be 'root'...

In my opinion, the CLI command 'qm' has a bug. It reports incorrect VM status 'running' if VM paused. 1) I am logged in as root. 2) Suspends the VM 114 ~# qm suspend 114 Proxmox VE Web-GUI reports the correct status 'paused' 3) Query the current status at CLI ~# qm status 114 or ~# qm...