Similar to #11, but uses TypeSet instead of TypeMap. This is correct for schemas that require predefined keys. It will break existing HCL configuration that sets geolocation using the old map syntax. Note the missing = below.
The provider will also break if it attempts to import state that has stored geolocation as a Map rather than a Set. State will need to be removed and re-imported.
The changes have only been applied to a records and cname records because these are the records we use. I think the same problem is present in other record types - not sure, haven't checked. May be worth fixing those later.
Similar to #11, but uses TypeSet instead of TypeMap. This is correct for schemas that require predefined keys. It will break existing HCL configuration that sets geolocation using the old map syntax. Note the missing
=
below.would need to be converted to
The provider will also break if it attempts to import state that has stored geolocation as a Map rather than a Set. State will need to be removed and re-imported.
The changes have only been applied to a records and cname records because these are the records we use. I think the same problem is present in other record types - not sure, haven't checked. May be worth fixing those later.