v1.4.0 (and in particular #35) added rfc4193 and sixplane address calculations to member.go. As I understand it, this should expose the RFC4193 and 6PLANE addresses from the zerotier_member resource through the rfc4193 and sixplane properties, respectively. However, the addresses I'm getting from those properties are as follows:
the sixplane property seems to contain /128 addresses with format fd...9993... (which I'm pretty sure should actually be RFC4193 addresses?)
the rfc4193 property seems to contain /80 addresses with format fc...::1 (which I'm pretty sure should actually be 6PLANE addresses?)
I often get confused when troubleshooting whether I flipped something incorrectly - am I understanding the situation correctly as a bug in terraform-provider-zerotier@v1.4.0, or is this some other confusion on my part?
v1.4.0 (and in particular #35) added rfc4193 and sixplane address calculations to member.go. As I understand it, this should expose the RFC4193 and 6PLANE addresses from the
zerotier_member
resource through therfc4193
andsixplane
properties, respectively. However, the addresses I'm getting from those properties are as follows:sixplane
property seems to contain /128 addresses with formatfd...9993...
(which I'm pretty sure should actually be RFC4193 addresses?)rfc4193
property seems to contain /80 addresses with formatfc...::1
(which I'm pretty sure should actually be 6PLANE addresses?)These observations appear to be consistent with how the addresses are calculated in the code: https://github.com/zerotier/terraform-provider-zerotier/blob/e57bb0f4be482b3cc93f91aa9f3e521670b16bfb/pkg/zerotier/member.go#L172-L181
I often get confused when troubleshooting whether I flipped something incorrectly - am I understanding the situation correctly as a bug in terraform-provider-zerotier@v1.4.0, or is this some other confusion on my part?