You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a number of issues making importing this resource inoperable. See apache/cloudstack#7837.
Additionally, it looks like the resource is comparing the name to traffictype.
// Set the type attribute - use the original value from the API call// If the Name field is empty, use a default value based on the traffic type IDiftt.Name!="" {
d.Set("traffic_type", tt.Name)
} else {
// Use a default value based on common traffic types// This is a fallback and might not be accurated.Set("traffic_type", "Management")
}
Traffic type isn't set in the API spec. Oddly, as noted in this thread, it is returned in the response.
Exactly. It could be fixed, by changing the json name to traffictype maybe, but that entirely depends on what the underlying library sends you. If it sends you incorrect data, then there's not a lot to be done.
Unfortunately this makes the plugin useless for managing cloudstack infrastructure. :(
Activity
kiranchavala commentedon Oct 17, 2025
@ilsaloving-gander I am unable to reproduce the issue
Get the traffic type id from cmk
ilsaloving-gander commentedon Oct 17, 2025
That's because you loaded a management one. Load one that isn't management.
kiranchavala commentedon Oct 17, 2025
Thanks @ilsaloving-gander was able to reproduce the issue
@Pearl1594 can you take a look at this issue
Steps to reproduce the issue
poddm commentedon Oct 17, 2025
There are a number of issues making importing this resource inoperable. See apache/cloudstack#7837.
Additionally, it looks like the resource is comparing the
nametotraffictype.Traffic type isn't set in the API spec. Oddly, as noted in this thread, it is returned in the response.
ilsaloving-gander commentedon Oct 17, 2025
Exactly. It could be fixed, by changing the json name to
traffictypemaybe, but that entirely depends on what the underlying library sends you. If it sends you incorrect data, then there's not a lot to be done.Unfortunately this makes the plugin useless for managing cloudstack infrastructure. :(
Pearl1594 commentedon Oct 20, 2025
Will address this - but this may not go into the 0.6.0 release of the provider as this requires a change upstream.
ilsaloving-gander commentedon Oct 20, 2025
What do you need me to do? The output from the PR looks good, I guess?
kiranchavala commentedon Oct 21, 2025
@ilsaloving-gander i have tested pr and its working fine
Moving it next milestone release of terraform 0.7 as it needs a newer cloudstack release and cloudstack-go release for it to work.
sudo87 commentedon Aug 11, 2026
Since it depends on apache/cloudstack-go#126 and apache/cloudstack-go#127 and both are not due to release, this issue cant be fixed, removing 0.7.0 milestone