Prepare provider for public Terraform Registry publishing

examples/data-sources/dynu_dns_records/data-source.tf

@@ -1,7 +1,8 @@
 terraform {
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }

examples/data-sources/dynu_domain/data-source.tf

@@ -1,7 +1,8 @@
 terraform {
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }

examples/data-sources/dynu_domains/data-source.tf

@@ -1,7 +1,8 @@
 terraform {
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }

examples/live_end_to_end_dns_zone/README.md

@@ -19,7 +19,7 @@ This example performs full live validation of the Dynu provider lifecycle by cre
 
 ## Prerequisites
 
-- A local build of this provider with Terraform `dev_overrides` for `dynu/dynu`.
+- A local build of this provider with Terraform `dev_overrides` for `beatz174-bit/dynu`.
 - Dynu API key provided as Terraform variable `dynu_api_key` (for example via `terraform.tfvars`).
 - A disposable domain value for `test_domain`.
 

examples/live_end_to_end_dns_zone/main.tf

@@ -1,7 +1,8 @@
 terraform {
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }

examples/live_safe_dns_record/README.md

@@ -17,7 +17,7 @@ Using a single suffix (`test_suffix`), this example creates five DNS record scen
 
 ## Prerequisites
 
-- Local provider binary + Terraform `dev_overrides` for `dynu/dynu`
+- Local provider binary + Terraform `dev_overrides` for `beatz174-bit/dynu`
 - `dynu_api_key` set in `terraform.tfvars`
 - A Dynu-managed root domain you control
 

examples/live_safe_dns_record/main.tf

@@ -1,5 +1,5 @@
 # Local development note:
-# Keep source as "dynu/dynu" and use ~/.terraformrc dev_overrides to point to
+# Keep source as "beatz174-bit/dynu" and use ~/.terraformrc dev_overrides to point to
 # your local terraform-provider-dynu binary during provider development.
 provider "dynu" {
   api_key = var.dynu_api_key

examples/live_safe_dns_record/versions.tf

@@ -3,7 +3,8 @@ terraform {
 
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }

examples/provider/provider.tf

@@ -1,7 +1,8 @@
 terraform {
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }

examples/read_only/providers.tf

@@ -3,13 +3,14 @@ terraform {
 
   required_providers {
     dynu = {
-      source = "dynu/dynu"
+      source  = "beatz174-bit/dynu"
+      version = "~> 0.1.0"
     }
   }
 }
 
 # Local development note:
-# This source address stays "dynu/dynu" while using ~/.terraformrc dev_overrides.
+# This source address stays "beatz174-bit/dynu" while using ~/.terraformrc dev_overrides.
 # Terraform will load your local terraform-provider-dynu binary instead of the public registry.
 provider "dynu" {
   # Set var.dynu_api_key in terraform.tfvars.