Inconsistencies in Linode ID type

[tchinmai7]

The Linode ID is returned as string in the Instance API - https://marketplace.upbound.io/providers/linode/provider-linode/v0.0.4/resources/instance.linode.upbound.io/Instance/v1alpha1#doc:status-atProvider-id

However, it is required to be passed as a number in other areas -
Volume - https://marketplace.upbound.io/providers/linode/provider-linode/v0.0.4/resources/volume.linode.upbound.io/Volume/v1alpha1#doc:spec-forProvider-linodeId

IPs - https://marketplace.upbound.io/providers/linode/provider-linode/v0.0.4/resources/instance.linode.upbound.io/IP/v1alpha1#doc:spec-forProvider-linodeId

SharedIPs - https://marketplace.upbound.io/providers/linode/provider-linode/v0.0.4/resources/instance.linode.upbound.io/SharedIPs/v1alpha1#doc:spec-forProvider-linodeId

[alvesoliveira1]

Hey, guys! I know this isn't the best place to ask, but do you have any plans to release an alpha version for this provider? Today we are discussing the best way to adopt Linode/Akamai Cloud for some projects and I think Crossplane can help us a lot to solve some limitations that the current version of Linode computing products have.

[srust]

Hi @alvesoliveira1 ! Thanks for asking.

We have had a lot of interest in having a Crossplane provider. We will work on getting a beta release of this provider ASAP. Please be on the lookout.

[cmcgalliard]

closing - stale