[GH-ISSUE #239] The cloud-init image is not regenerated #50

Open
opened 2026-02-28 00:40:21 +03:00 by kerem · 1 comment
Owner

Originally created by @cedrictabary on GitHub (Feb 16, 2023).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/239

I am using the terraform provider for proxmox and it seems that it is missing some method here to call the API to regenerate cloud-init image ?

I found this issue on the proxmox provider repo, but it was closed :
https://github.com/Telmate/terraform-provider-proxmox/issues/160

Originally created by @cedrictabary on GitHub (Feb 16, 2023). Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/239 I am using the terraform provider for proxmox and it seems that it is missing some method here to call the API to regenerate cloud-init image ? I found this issue on the proxmox provider repo, but it was closed : https://github.com/Telmate/terraform-provider-proxmox/issues/160
Author
Owner

@sebastian-de commented on GitHub (Mar 5, 2023):

To regenerate the Cloud-Init image, one has to delete it and add a new one:
https://forum.proxmox.com/threads/regenerate-cloud-init-image-using-ansible.89964/post-455096

In Packer we're doing it the same way: Delete the drive first, then add it again:
https://github.com/hashicorp/packer-plugin-proxmox/pull/139

<!-- gh-comment-id:1455003153 --> @sebastian-de commented on GitHub (Mar 5, 2023): To regenerate the Cloud-Init image, one has to delete it and add a new one: https://forum.proxmox.com/threads/regenerate-cloud-init-image-using-ansible.89964/post-455096 In Packer we're doing it the same way: Delete the drive first, then add it again: https://github.com/hashicorp/packer-plugin-proxmox/pull/139
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/proxmox-api-go#50
No description provided.