How to migrate from the Nebius registry to the Terraform Registry

​

How to check your registry

1. Find terraform.tf or another file that contains the top-level terraform block.
2. In the required_providers block, find the nebius provider and check its source address in source:
   terraform {
     required_providers {
       nebius = {
         source  = "terraform-provider.storage.eu-north1.nebius.cloud/nebius/nebius"
         version = ">= 0.5.210"
       }
     }
   }
   

3. Depending on the source address, do one of the following:
   • source = "nebius/nebius": the configuration already uses the Terraform Registry. No action is required, so you can stop here.
   • source = "terraform-provider.storage.eu-north1.nebius.cloud/nebius/nebius" or source = "terraform-provider-nebius.storage.ai.nebius.cloud/nebius/nebius": the configuration uses a Nebius registry. Migrate it as described in How to update your registry.

​

How to update your registry

1. Upgrade to the most recent 0.5.x version:
   1. Check the most recent 0.5.x version in the release notes.
   2. In terraform.tf, update the version constraint:
      terraform {
        required_providers {
          nebius = {
            source  = "terraform-provider.storage.eu-north1.nebius.cloud/nebius/nebius"
            version = ">= 0.5.210"
            version = ">= <most_recent_0.5.x_version>"
          }
        }
      }
      
   3. Re-initialize the working directory:
      terraform init -upgrade
      
   4. Check that the configuration works with the new version:
      terraform plan
      
      The plan must complete without errors before you replace the source address.
2. Replace the source address and upgrade from 0.5.x to the latest published version in the Terraform Registry:
   1. In terraform.tf, update the source address and the version constraint:
      terraform {
        required_providers {
          nebius = {
            source  = "terraform-provider.storage.eu-north1.nebius.cloud/nebius/nebius"
            version = ">= <most_recent_0.5.x_version>"
            source  = "nebius/nebius"
            version = ">= <latest_version>"
          }
        }
      }
      
      Specify the latest provider version published in the Terraform Registry. Although it’s allowed to omit the version constraint, Terraform strongly recommends specifying it explicitly.
   2. In the root module or workspace that owns the Terraform state, replace the provider address in the state:
      terraform state replace-provider \
        terraform-provider.storage.eu-north1.nebius.cloud/nebius/nebius \
        registry.terraform.io/nebius/nebius
      terraform state replace-provider \
        terraform-provider-nebius.storage.ai.nebius.cloud/nebius/nebius \
        registry.terraform.io/nebius/nebius
      
      The commands back up the state file, terraform.tfstate, before updating it.
   3. Re-initialize the working directory:
      terraform init -upgrade
      
3. Check that the configuration uses the new source address and still works:
   terraform providers
   terraform plan
   
   The outputs must only reference registry.terraform.io/nebius/nebius. If they still reference terraform-provider.storage.eu-north1.nebius.cloud/nebius/nebius or terraform-provider-nebius.storage.ai.nebius.cloud/nebius/nebius, perform the migration on nested modules that still use old source addresses for the provider. The plan must complete without errors. If the plan reports an error for a resource or an attribute, find the change that caused it under BREAKING CHANGES in the releases and update your configuration accordingly.
4. If your configuration is under version control, commit the changes that you made to it, including the updated dependency lock file (.terraform.lock.hcl).