Support for "hardware mapping" as dedicated Terraform resource & data source about terraform-provider-proxmox HOT 4 CLOSED

Hi @svengreb! 👋🏼

Thank you for the suggestion. I'm totally on board with configuring PCI mapping through a resource. Even though I don't play around with mapped devices in my home lab, I'd love some help getting this feature up and running!

If you (or anyone else! 😄) want to jump in and contribute, we've got two main things to tackle: setting up an API wrapper around the Proxmox REST API in /proxmox, and creating the resource itself in /fwprovider. The most recent resources/datasources were created using the TF Plugin Framework, and you can use the code under /fwprovider as an example.

Feel free to drop any questions here or, better yet, open a pull request. Any contributions and insights will be much appreciated!

from terraform-provider-proxmox.

Just a quick update: I started (and almost completed) the implementation while running it against my own homelab, just in case someone wanted to pick this issue up and we end up with duplicated PRs in the end 😄

from terraform-provider-proxmox.

@bpg The PR is finally submitted: #1213 🎉

Took some time again because I refactored my first revision that used some generic code to "prevent" to create dedicated resources & data sources for each bus type (PCI and USB), but the Terraform Plugin Framework is designed to enforce explicit and non-abstract implementations so I restored by previous implementation agin, which is the state that is now available in the PR.

from terraform-provider-proxmox.

Thanks for the tips to get started in this repository! 👍🏼
I've planned to implement it within the next weeks, but of course everyone who reads this ticket can pick it up.

from terraform-provider-proxmox.