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
ClusterType is not being populated after calling ListAllKubernetesVersions. This means it's not possible to know what ClusterType to use when provisioning specific versions. We need this fix to correctly provision CIVO clusters in Portainer.
The problem is caused by the json tag on the KubernetesVersion type
To unmarshal JSON into a struct, Unmarshal matches incoming object keys to the keys used by Marshal (either the struct field name or its tag), preferring an exact match but also accepting a case-insensitive match. By default, object keys which don't have a corresponding struct field are ignored (see Decoder.DisallowUnknownFields for an alternative).
In the case above, it uses the case-insensitive match. All the other fields following the same pattern even thought the API returns Pascal case field names.
ClusterType
is not being populated after callingListAllKubernetesVersions
. This means it's not possible to know whatClusterType
to use when provisioning specific versions. We need this fix to correctly provision CIVO clusters in Portainer.The problem is caused by the json tag on the
KubernetesVersion
typeIt should be
and not
The rules of naming being.
In the case above, it uses the case-insensitive match. All the other fields following the same pattern even thought the API returns Pascal case field names.
example response from the versions API.
The text was updated successfully, but these errors were encountered: