mirror of
https://github.com/Telmate/proxmox-api-go.git
synced 2026-04-25 23:45:55 +03:00
[GH-ISSUE #496] meta: state of the cli #135
Labels
No labels
good first issue
issue/confirmed
issue/critical
proposal/accepted
pull-request
type/bug
type/enhancement
type/feature
type/question
type/refactoring
type/testing
type/testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmox-api-go#135
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 @NemoDacremont on GitHub (Oct 29, 2025).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/496
When I worked on the README, I realized that some features were missing from the new CLI and were only present on the legacy one. I think the state of the CLI is confusing, and it would be better to only have the new one.
We discussed redesigning the public interface of the client, I actually changed my mind and think the interface you proposed is really interesting, but I think it would be time-consuming. Redesigning the public interface would help new user working on the project, however I think the CLI is also a good way to understand how the SDK works, and having it up to date and clear is important to this end.
I think I'll try to work a little bit on this before going back to SDNs for the terraform provider, what do you think about migrating the legacy CLI to the new one @Tinyblargon ? Is it possible to remove the legacy CLI, or may it risk breaking things ?
get guest networkinterfacesguest installguest clonesshsshguest sendstringguest migrateupdate acmeaccountI'll edit this post with the other migration tasks.
@Tinyblargon commented on GitHub (Oct 29, 2025):
@NemoDacremont with the old CLI, we should switch the flag, make the legacy one opt-in. It would also be a good moment to start with a
0.0.0and start shipping binaries of the CLI.For refactoring the public interferences. I effectively have about four howers of "dead time" due to work travel with public transit. I try to do the boring busy work of the codebase during that time.
As for the SDN feature, we will have to go through a few rounds of review with the public interfaces as it's a really complex feature.
@NemoDacremont commented on GitHub (Oct 29, 2025):
ok, then if that's fine with you I'll go ahead and start migrating the features to the new cli in small PR if possible, once that's done i'll make the legacy CLI opt in.