packetfabric_cs_azure_hosted_connection: json: cannot unmarshal string into Go struct field about terraform-provider-packetfabric HOT 5 CLOSED

Hi @rjouhann, I believe there's a discrepancy between docs and the API. Since we're relying on docs as our source of truth, it shows both ifd_port_circuit_id_cust and ifd_port_circuit_id_pf with int values.

Please see this link for reference (https://docs.packetfabric.com/api/v2/redoc/#tag/Cloud-Services-Azure/operation/azure_hosted_connection_post)

from terraform-provider-packetfabric.

Hey @pontovinte, in the link you shared, the port is a string, not an int.

port | required | string The port to connect to Azure.

Example: "port": "PF-AP-LAX1-1002",

from terraform-provider-packetfabric.

@rjouhann, either port is string (here) and ifd_port_circuit_id_cust is int (here). The issue above was complaining about ifd_port_circuit_id_cust not being parsed correctly. But I'm confused if there's any discrepancy between API doc and the actual API as I explained here

from terraform-provider-packetfabric.

@pontovinte I understand the confusion the ifd_port_circuit_id_cust and ifd_port_circuit_id_pf are part of the API response, not the body of the request.

To my knowledge and understanding, ports which is part of the body of the request is always a string because there is always a prefix and PoP name like PF-AP-LAX-1234 and sometime a suffix like PF-AP-LAX-1234-PF.

I actually tried to create a connection using /services/cloud/hosted/azure and look what I am getting in the response:

    "components": {
        "ifd_port_circuit_id_cust": "PF-AP-LAX2-1729130",

ifd_port_circuit_id_cust is a string. I will follow up with PF dev team and get the API schema example updated so it uses a string, not an int for ifd_port_circuit_id_cust and ifd_port_circuit_id_pf response examples.

But the schema does say those are string:

from terraform-provider-packetfabric.

Verified fix in feature/google-service branch

from terraform-provider-packetfabric.