mirror of
https://github.com/Telmate/proxmox-api-go.git
synced 2026-04-25 15:35:51 +03:00
[GH-ISSUE #358] Hide cloud-init data when no cloud-init disk is present? #87
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#87
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 @Tinyblargon on GitHub (Aug 16, 2024).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/358
Should we return a
ConfigQemu.CloudInitobject when no cloud-init disk has been configured?When no cloud-init disk is configured the settings don't do anything. The PVE gui still shows the information all be it grayed out.
I do feel like checking if
ConfigQemu.CloudInit == nilis the most intuitive way of checking if the vm uses cloud-init settings.The alternative would be to check if a cloud-init disk is configured and check if
ConfigQemu.CloudInit == nil.Making users check if a cloud-init disk is configured feels like a lot to ask, especially with how the disks are implemented.
so we should make
ConfigQemu.CloudInit = nilwhen no cloud-init disk is configured.@mleone87 whats your opinion on this?
github.com/Telmate/proxmox-api-go@602cfe748b/proxmox/config_qemu.go (L32-L39)