Sync open source content 🐝 (from 645291dd5c2b8c37cf42d63b074ecfcc90da44a7)

Author: beezythebot

docs/speakeasy-reference/generation/terraform-config.mdx

@@ -25,13 +25,22 @@ terraform:
       name: "packageName",
       required: "true",
       default: "terraform",
-      description: "Terraform Provider name. Prefixes all resource names. For providers published in the public Terraform Registry, this typically matches the suffix after terraform-provider- in the GitHub Repository name.",
+      description:
+        "Terraform Provider name. Prefixes all resource names unless `providerTypeNameOverride` is set. For providers published in the public Terraform Registry, this typically matches the suffix after terraform-provider- in the GitHub Repository name.",
     },
     {
       name: "author",
       required: "true",
       default: "speakeasy",
-      description: "Terraform Provider namespace. For providers published in the public Terraform Registry, this typically matches the GitHub Organization name.",
+      description:
+        "Terraform Provider namespace. For providers published in the public Terraform Registry, this typically matches the GitHub Organization name.",
+    },
+    {
+      name: "providerTypeNameOverride",
+      required: "false",
+      default: "",
+      description:
+        "Overrides the provider type name used for resource naming. When set, this value is used as the prefix for all resource, data source, ephemeral resource, and action type names instead of `packageName`. This is useful for variant providers that need to use the same resource names as another provider (e.g. a beta provider sharing resource names with the main provider).",
     },
   ]}
   columns={[
@@ -80,7 +89,7 @@ terraform:
       required: "false",
       default: "[]",
       description:
-        "A list of `{ importLocation?: string, importAlias?: string, datasource: string }` objects to insert into the provider ephemeral resource list.",
+        "A list of `{ importLocation?: string, importAlias?: string, resource: string }` objects to insert into the provider ephemeral resource list.",
     },
   ]}
   columns={[

docs/terraform/customize-terraform/provider-configuration.mdx

@@ -217,3 +217,34 @@ The `additionalActions` key is expected to contain a list of `{ importLocation?:
 The `additionalFunctions` key is expected to contain a list of `{ importLocation?: string, importAlias?: string, function: string }` objects. Each `function` is inserted into the provider-managed function list. If `importLocation` or `importAlias` is defined, Speakeasy adds them to the import list at the top of the provider file.
 
 To learn more about how to write a Terraform resource, please consult the [official Terraform documentation](https://developer.hashicorp.com/terraform/plugin/framework).
+
+## Override provider type name
+
+<Callout title="Uncommon customization" type="info">
+  Most providers should omit `providerTypeNameOverride` and rely on the default
+  behavior of prefixing resource type names with `packageName`. Only use this
+  configuration to ship a variant provider that must share resource type names
+  with another provider.
+</Callout>
+
+By default, Terraform resource and action type names are prefixed with the `packageName` value from `gen.yaml`. Set the `providerTypeNameOverride` configuration to replace that prefix with a different value, while retaining `packageName` for Go module naming, binary naming, and Terraform Registry publishing.
+
+The common use case for this is supporting a variant provider, such as a beta provider, that intentionally shares resource type names with a related provider. It mirrors the `google` and `google-beta` provider pattern, where both providers expose the same resource type names so Terraform configurations can switch between them using the [`provider` meta-argument](https://developer.hashicorp.com/terraform/language/meta-arguments/resource-provider).
+
+In this example, a beta provider published as `examplecloud-beta` exposes resources with the `examplecloud` prefix to match the stable `examplecloud` provider:
+
+```yaml
+terraform:
+  packageName: examplecloud-beta
+  providerTypeNameOverride: examplecloud
+```
+
+Without this configuration, resources would be named `examplecloud-beta_thing`. With this configuration, resources are instead named `examplecloud_thing`, matching the resource type names of the stable provider. Terraform configurations can then select the beta implementation using the `provider` meta-argument:
+
+```hcl
+resource "examplecloud_thing" "example" {
+  provider = examplecloud-beta
+
+  # ...
+}
+```