-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue 196] feature: datasource to find VM in cluster #295
base: main
Are you sure you want to change the base?
Conversation
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
2599b9a
to
155f985
Compare
Basic configuration verification copied from builder. Template in directory test-fixtures works.
155f985
to
5740ec7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your solid contribution!
I've left 2 comments but it seems pretty good.
Used anonymous functions instead of a bunch of named ones.
Renamed package and corrected documentation accordingly.
In the process of renaming the function and editing the documentation, I noticed two edge cases and fixed them |
I have implemented a datasource which was described in #196.
This datasource searches the PVE cluster for some VMs that matches specified filters and returns VM ID for one (and only one) guest. I have chosen such behavior because it will be straightforward for
proxmox-clone
builder - there will be no need for user to manipulate lists inlocals
.I have included some tests and documentation for datasource (but since this is my very first attempt to publish my work for Packer I may have missed something).
This datasource uses undocumented
meta
field from Proxmox API responses. (But the Proxmox team recommended using this field to determine guest creation time in the forum messages).Closes #196