Supported Provider Versions

A provider is a plug-in that encapsulates various resource APIs (such as CRUD APIs) for the resource formation engine to call. Since providers are under active development, earlier versions might have functional issues. To guarantee a smooth experience, you are advised to use the latest version.

• Best Practices

Use the greater-than (>) or greater-than-or-equal-to (>=) operator to explicitly define a version constraint within which any provider versions compatible with RFS can be used.

The following sample serves as a reference for HCL templates.

terraform {
    required_providers {
      huaweicloud = {
        source = "huawei.com/provider/huaweicloud"
        version = ">= 1.70.1"
        }
    }
}

{
    "terraform":{
        "required_providers":[
            {
                "huaweicloud":{
                    "source":"huawei.com/provider/huaweicloud",
                    "version":">= 1.70.1"
                }
            }
        ]
    }
}

• Provider Upgrade

  If you deploy a stack or stack set using an outdated provider and then try to redeploy, delete, or roll the stack or stack set back, you may receive an error stating, "no available release match the given constraints x.x.x." To resolve this, use > or >= to update the version constraint in your template. Once you redeploy with the provider, it will upgrade to the latest version.

  Similarly, if you are applying an execution plan with an outdated provider, you might see the same error message ("no available release match the given constraints x.x.x") during the deployment process. In this case, deleting the execution plan is still possible. To fix the issue, create an execution plan from the template with the updated provider and apply the plan again.

  If you need to access a provider that has been taken offline, utilize the custom provider function.

• Maintained Providers

The following table lists the supported provider type and its versions and end of service (EOS) dates.