silo early access features in a `-early-access` or `-beta` provider

[StephenWithPH]

Checklist

• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

I periodically see changes to this provider that add support for early-access features; #1494 released in v1.41.0 is the most recent example.

Per the Auth0 docs:

Early Access releases are new or enhanced features made available for you to selectively opt-in to and use in both production and non-production environments. Minor changes can be expected on the road to General Availability. Early Access releases may be restricted to a select number of subscribers or rolled out to a subset of tenants (i.e. available only to tenants hosted in Japan).

Right now, if we update our provider version and happen to get EA feature changes, we may experience frustrating behavior:

• apply fails because we have not opted in to EA
• apply fails because the EA feature is not enabled (yet) in our tenant due to Auth0's gradual rollout policy
• apply succeeds, mutating some resource with an EA feature that we don't want (since it is EA)

Describe the ideal solution

The GCP provider is a good example of how to handle this: https://registry.terraform.io/providers/hashicorp/google/latest/docs#releases

Specifically, they release the same provider as "normal" and -beta, and specific features are only available when users select the google-beta provider on a specific resource:

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/api_gateway_api (just one example)

I believe a similar approach here would deliver a better experience for users of this provider.

Alternatives and current workarounds

Either we don't take an updated version of this provider, or we manually remediate any problems that a given implicitly-EA resource causes.

Additional context

No response

[bkiran6398]

Hi @StephenWithPH,

Thank you for this well-thought-out feature request. The pain points you've described around EA features causing unexpected failures are spot on, and the GCP google-beta provider reference is a great model to consider.

Our team will evaluate the right approach, weighing factors like maintenance overhead, developer experience, and release complexity to ensure we land on a solution that genuinely helps both EA adopters and stable-channel users. We're planning to tackle this in the coming quarter and will keep this issue updated as we progress.