0
0
mirror of https://github.com/bpg/terraform-provider-proxmox.git synced 2025-07-03 03:52:58 +00:00
terraform-provider-proxmox/fwprovider/hardwaremapping/datasource.go
Sven Greb 76c1c2282b
feat(cluster): Implement initial support for "hardware mappings" (#1213)
* feat(cluster): Implement initial support for "hardware mappings"

Right now it is alredy possible to use a mapped resource [1], but there
is no dedicated `proxmox_virtual_environment_cluster_hardware_mapping`
resource but this step must still be done manually (or automated through
other ways that interact with the Proxmox API).

This commit implements support for "hardware mapping" resources and data
sources for the, currently, available bus types PCI and USB, based on
the Proxmox VE API documentations [2].

There are some "specialities" in these resources and data sources:

1. The Proxmox VE API attribute, but this implementations names it
   "comment" since this naming is generally across the Proxmox VE web UI
   and API documentations. This still follows the Terraform
   "best practices" [3] as it improves the user experience by matching
   the field name to the naming used in the human-facing interfaces.

2. Like in point 1, the name of the attribute of "node checks
   diagnostics" for USB hardware mappings is "errors" in the Proxmox VE
   API while it is "checks" for hardware mappings of type PCI.
   The second naming pattern is also generally used across the
   Proxmox VE web UI and API documentations, including the "check_node"
   attribute that is also implemented in the
   "proxmox_virtual_environment_hardware_mappings" data source.
   Therefore, this implementation named both attributes "checks" which
   still follows the Terraform "best practices" [3] as it improves the
   user experience by matching the field name to the naming used in the
   human-facing interfaces.
3. This implmenetation comes with the "unique" feature of allowing
   comments (named "descriptions" by the Proxmox VE API) for an entry in
   a device map which is not possible through the web UI at all but only
   adding a comment for the whole mapping entry instead.

Note that this implementation also adds another point in the
"Known Issues" documentation since it is only possible to map a
PCI/USB device using the `root` PAM account, but this is still better
than having to manually configure it through the web UI or by
interacting with the Proxmox VE API on other ways.

[1]: https://github.com/bpg/terraform-provider-proxmox/pull/500
[2]: https://pve.proxmox.com/pve-docs/api-viewer/#/cluster/mapping/pci
[3]: https://developer.hashicorp.com/terraform/plugin/best-practices/hashicorp-provider-design-principles#resource-and-attribute-schema-should-closely-match-the-underlying-api

Signed-off-by: Sven Greb <development@svengreb.de>

* fix linter

Signed-off-by: Pavel Boldyrev <627562+bpg@users.noreply.github.com>

---------

Signed-off-by: Sven Greb <development@svengreb.de>
Signed-off-by: Pavel Boldyrev <627562+bpg@users.noreply.github.com>
Co-authored-by: Pavel Boldyrev <627562+bpg@users.noreply.github.com>
2024-04-18 16:00:51 -04:00

206 lines
6.6 KiB
Go

/*
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at https://mozilla.org/MPL/2.0/.
*/
package hardwaremapping
import (
"context"
"fmt"
"slices"
"strings"
"github.com/hashicorp/terraform-plugin-framework-validators/stringvalidator"
"github.com/hashicorp/terraform-plugin-framework/attr"
"github.com/hashicorp/terraform-plugin-framework/datasource"
"github.com/hashicorp/terraform-plugin-framework/datasource/schema"
"github.com/hashicorp/terraform-plugin-framework/schema/validator"
"github.com/hashicorp/terraform-plugin-framework/types"
"github.com/bpg/terraform-provider-proxmox/fwprovider/structure"
"github.com/bpg/terraform-provider-proxmox/proxmox"
"github.com/bpg/terraform-provider-proxmox/proxmox/cluster/mapping"
proxmoxtypes "github.com/bpg/terraform-provider-proxmox/proxmox/types/hardwaremapping"
)
// Ensure the implementation satisfies the required interfaces.
var (
_ datasource.DataSource = &dataSource{}
_ datasource.DataSourceWithConfigure = &dataSource{}
)
// dataSource is the data source implementation for a hardware mapping.
type dataSource struct {
client *mapping.Client
}
// Configure adds the provider-configured client to the data source.
func (d *dataSource) Configure(_ context.Context, req datasource.ConfigureRequest, resp *datasource.ConfigureResponse) {
if req.ProviderData == nil {
return
}
client, ok := req.ProviderData.(proxmox.Client)
if !ok {
resp.Diagnostics.AddError(
"Unexpected Resource Configure Type",
fmt.Sprintf("Expected *proxmox.Client, got: %T", req.ProviderData),
)
return
}
d.client = client.Cluster().HardwareMapping()
}
// Metadata returns the data source type name.
func (d *dataSource) Metadata(_ context.Context, req datasource.MetadataRequest, resp *datasource.MetadataResponse) {
resp.TypeName = req.ProviderTypeName + "_hardware_mappings"
}
// Read fetches the list of hardware mappings from the Proxmox VE API then converts it to a list of strings.
func (d *dataSource) Read(ctx context.Context, req datasource.ReadRequest, resp *datasource.ReadResponse) {
var hm model
resp.Diagnostics.Append(req.Config.Get(ctx, &hm)...)
if resp.Diagnostics.HasError() {
return
}
hmType, err := proxmoxtypes.ParseType(hm.Type.ValueString())
if err != nil {
resp.Diagnostics.AddError("Could not parse hardware mapping type", err.Error())
return
}
list, err := d.client.List(ctx, hmType, hm.CheckNode.ValueString())
if err != nil {
resp.Diagnostics.AddError(
"Unable to read hardware mappings",
err.Error(),
)
return
}
createCheckDiagnostics := func(hmID string, input []mapping.NodeCheckDiag) []modelNodeCheckDiag {
checks := make([]modelNodeCheckDiag, len(input))
for idx, check := range input {
m := modelNodeCheckDiag{
MappingID: types.StringValue(hmID),
Severity: types.StringPointerValue(check.Severity),
}
// Strip the unnecessary new line control character (\n) from the end of the message that is, for whatever reason,
// returned this way by the Proxmox VE API.
msg := strings.TrimSuffix(types.StringPointerValue(check.Message).ValueString(), "\n")
m.Message = types.StringPointerValue(&msg)
checks[idx] = m
}
return checks
}
mappings := make([]attr.Value, len(list))
for idx, data := range list {
mappings[idx] = types.StringValue(data.ID)
// One of the fields only exists when the "check-node" option was passed to the Proxmox VE API with a valid node
// name.
// Note that the Proxmox VE API, for whatever reason, only returns one error at a time, even though the field is an
// array.
if (data.ChecksPCI != nil && len(data.ChecksPCI) > 0) || (data.ChecksUSB != nil && len(data.ChecksUSB) > 0) {
switch data.Type {
case proxmoxtypes.TypePCI:
hm.Checks = append(hm.Checks, createCheckDiagnostics(data.ID, data.ChecksPCI)...)
case proxmoxtypes.TypeUSB:
hm.Checks = append(hm.Checks, createCheckDiagnostics(data.ID, data.ChecksUSB)...)
}
}
// Ensure to keep the order of the diagnostic entries to prevent random plan changes.
slices.SortStableFunc(
hm.Checks, func(a, b modelNodeCheckDiag) int {
return strings.Compare(a.MappingID.ValueString(), b.MappingID.ValueString())
},
)
}
values, diags := types.SetValue(types.StringType, mappings)
resp.Diagnostics.Append(diags...)
if resp.Diagnostics.HasError() {
return
}
hm.MappingIDs = values
hm.ID = types.StringValue("hardware_mappings")
resp.Diagnostics.Append(resp.State.Set(ctx, &hm)...)
}
// Schema returns the schema for the data source.
func (d *dataSource) Schema(
_ context.Context,
_ datasource.SchemaRequest,
resp *datasource.SchemaResponse,
) {
resp.Schema = schema.Schema{
Description: "Retrieves a list of hardware mapping resources.",
Attributes: map[string]schema.Attribute{
schemaAttrNameChecks: schema.ListNestedAttribute{
Computed: true,
Description: `Might contain relevant diagnostics about incorrect configurations.`,
NestedObject: schema.NestedAttributeObject{
Attributes: map[string]schema.Attribute{
schemaAttrNameChecksDiagsMappingID: schema.StringAttribute{
Computed: true,
Description: "The corresponding hardware mapping ID of the node check diagnostic entry.",
},
schemaAttrNameChecksDiagsMessage: schema.StringAttribute{
Computed: true,
Description: "The message of the node check diagnostic entry.",
},
schemaAttrNameChecksDiagsSeverity: schema.StringAttribute{
Computed: true,
Description: "The severity of the node check diagnostic entry.",
},
},
},
},
schemaAttrNameCheckNode: schema.StringAttribute{
Description: "The name of the node whose configurations should be checked for correctness.",
Optional: true,
},
schemaAttrNameHWMIDs: schema.SetAttribute{
ElementType: types.StringType,
Computed: true,
Description: "The identifiers of the hardware mappings.",
},
schemaAttrNameTerraformID: structure.IDAttribute(
"The unique identifier of this hardware mappings data source.",
),
schemaAttrNameType: schema.StringAttribute{
Description: "The type of the hardware mappings.",
Required: true,
Validators: []validator.String{
stringvalidator.OneOf(
[]string{
proxmoxtypes.TypePCI.String(),
proxmoxtypes.TypeUSB.String(),
}...,
),
},
},
},
}
}
// NewDataSource returns a new data source for hardware mappings.
// This is a helper function to simplify the provider implementation.
func NewDataSource() datasource.DataSource {
return &dataSource{}
}