I was trying to use the terraform cloudstack provider but was getting hung up with the traffic types. I tracked it back to this library, which uses 'name' for the field instead of 'traffictype'.
What's even more frustrating is that the API documentation is similar. It uses name instead of traffictype.
Here is what I get when I do the request via cloudmonkey, and I confirmed I got the same results from CloudStack python package.
{
"count": 4,
"traffictype": [
{
"id": "b20ba0e0-5c8c-4cb7-ab68-8fe3e011a336",
"physicalnetworkid": "ad0e9614-6d9c-41c8-9459-7539673b2107",
"traffictype": "Guest"
},
{
"id": "9f2b4227-653c-4523-b848-4dc889e2c8ff",
"kvmnetworklabel": "cloudbr0",
"physicalnetworkid": "ad0e9614-6d9c-41c8-9459-7539673b2107",
"traffictype": "Management"
},
{
"id": "5de01b4b-1448-4ee6-af4c-529a50966527",
"kvmnetworklabel": "cloudbr0",
"physicalnetworkid": "ad0e9614-6d9c-41c8-9459-7539673b2107",
"traffictype": "Public"
},
{
"id": "52c4901f-467c-414d-9cdd-534a0fb8195e",
"kvmnetworklabel": "cloudbr0",
"physicalnetworkid": "ad0e9614-6d9c-41c8-9459-7539673b2107",
"traffictype": "Storage"
}
]
}
I was trying to use the terraform cloudstack provider but was getting hung up with the traffic types. I tracked it back to this library, which uses 'name' for the field instead of 'traffictype'.
What's even more frustrating is that the API documentation is similar. It uses name instead of traffictype.
Here is what I get when I do the request via cloudmonkey, and I confirmed I got the same results from CloudStack python package.