Convert the provider to a Provider Family

[displague]

What problem are you facing?

As the provider grows to cover more of the Equinix API surface area, the number of CRDs will expand.

Crossplane has adopted a concept called Provider Families, which improves the performance on K8s clusters in the presence of many CRDs.

This provider is in an early enough stage to adopt families now ahead of changes to add more resources. Because this provider is generated, these changes should be minimal.

• https://blog.crossplane.io/crd-scaling-provider-families/?utm_campaign=2023_Q2_EVER_GBL_CT_New-Provider-Families&utm_medium=slack&utm_source=crossplane&utm_term=blog&utm_content=new-provider-families-release
• https://github.com/crossplane/crossplane/blob/7fa9184/design/design-doc-smaller-providers.md

How could Equinix Provider help solve your problem?

Split the provider into families that align to the current API Groups:

• metal
• ne
• fabric

In the future, this could extend to other APIs (per https://developer.equinix.com/catalog):

• Customer Portal
• SmartView
• Internet Access
• Customer Resource Hierarchy
• Accounts and Authentication
• Digital LOA

Also see:

• Migration guide
• crossplane-community/#sig-provider-families

[aayushrangwala]

/assign @aayushrangwala

[displague]

An upstream PR related to provider families and groups is the split into separate pacakges, each with their own cmd/X/ main.go generated from a main.go.tmpl dependent on internal/controller
crossplane-contrib/provider-upjet-aws@5bb4816