Does the PR have any schema changes?

Does the PR have any schema changes?

Found 10 breaking changes:

Types

• "equinix:networkedge/getDeviceClusterDetailNode0VendorConfiguration:getDeviceClusterDetailNode0VendorConfiguration": required:
  • 🟢 "licenseId" property has changed to Required
  • 🟢 "licenseKey" property has changed to Required
  • 🟢 "privateAddress" property has changed to Required
  • 🟢 "privateCidrMask" property has changed to Required
  • 🟢 "privateGateway" property has changed to Required
• "equinix:networkedge/getDeviceClusterDetailNode1VendorConfiguration:getDeviceClusterDetailNode1VendorConfiguration": required:
  • 🟢 "licenseId" property has changed to Required
  • 🟢 "licenseKey" property has changed to Required
  • 🟢 "privateAddress" property has changed to Required
  • 🟢 "privateCidrMask" property has changed to Required
  • 🟢 "privateGateway" property has changed to Required

New functions:

• fabric/getCloudRouters.getCloudRouters
• fabric/getConnections.getConnections
• fabric/getNetworks.getNetworks

Maintainer note: consult the runbook for dealing with any breaking changes.

Although I think it's not a problem, you shouldn't add MaxItemsOne on all fields, it's a workaround for TypeSet/TypeList attributes which are actually a single nested object (terraform sdkv2 schema behavior), since pulumi renames them to their plural form (Pagnitation --> Paginations) if they do not have a Maxitems=1 defined in the terraform side. So we should really fix the problem on the Terraform side, instead of continuing to make the schema more complex on the Pulumi side.

Unless you know there's a TypeSet/List field in any of the new resources where we missed MaxItems=1, you can omit the whole Fields definition in all new resources/datasources:

"equinix_fabric_cloud_routers": {Tok: makeEquinixDataSource(fabricMod, "CloudRouters")},

We will remove the manual overrides and that we'll take a look into our schemas to have this updated when we can. Now that it's on our radar and we'll manage Pulumi in a more dedicated way.
Can we release the latest version without including these changes?