# Invalid legacy provider address

**URL:** <https://discuss.hashicorp.com/t/invalid-legacy-provider-address/52149>\
**Category:** Terraform\
**Created:** [March 31, 2023, 11:29am UTC](https://discuss.hashicorp.com/t/invalid-legacy-provider-address/52149 "2023-03-31T11:29:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![javed.alam1303](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@javed.alam1303](https://discuss.hashicorp.com/u/javed.alam1303)\
**Post date:** [March 31, 2023, 11:29am UTC](https://discuss.hashicorp.com/t/invalid-legacy-provider-address/52149/1 "2023-03-31T11:29:37Z")

</div>

Error: Invalid legacy provider address

This configuration or its associated state refers to the unqualified provider  
“postgresql”.

You must complete the Terraform 0.13 upgrade process before upgrading to later  
versions

My terraform version is: Terraform v0.14.2 (Let me know if I need to downgrade)

---

<div class="post-metadata">

**Author:** ![maxb](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/maxb/32/26655_2.png) [@maxb](https://discuss.hashicorp.com/u/maxb)\
**Post date:** [March 31, 2023, 12:20pm UTC](https://discuss.hashicorp.com/t/invalid-legacy-provider-address/52149/2 "2023-03-31T12:20:33Z")

</div>

1. Downgrade to Terraform 0.13

2. Run an **apply**. The apply **must** modify the state. If the apply says there are no changes to apply, temporarily add a `resource "null_resource" "some_name" {}` to your configuration, just so there is something to change. You can take it out again once the apply has happened.

1. Upgrade to Terraform 1.x, paying attention to the upgrade guides for the versions you pass.

---

<div class="post-metadata">

**Author:** ![javed.alam1303](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@javed.alam1303](https://discuss.hashicorp.com/u/javed.alam1303)\
**Post date:** [March 31, 2023, 1:43pm UTC](https://discuss.hashicorp.com/t/invalid-legacy-provider-address/52149/3 "2023-03-31T13:43:21Z")

</div>

@maxb Is it possible to schedule google meet ?? I’m confused here, why are you asking me to execute apply command, it will corrupt the previous \*state file isn’t it ? I do not wanna to mess the existing infrastructure.

---

<div class="post-metadata">

**Author:** ![maxb](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/maxb/32/26655_2.png) [@maxb](https://discuss.hashicorp.com/u/maxb)\
**Post date:** [March 31, 2023, 3:46pm UTC](https://discuss.hashicorp.com/t/invalid-legacy-provider-address/52149/4 "2023-03-31T15:46:37Z")

</div>

> [@javed.alam1303](#):
>
> Is it possible to schedule google meet ??

Sorry, no. I’m happy to respond here at my convenience, but I’m not here to provide free professional consultancy services.

> [@javed.alam1303](#):
>
> I’m confused here, why are you asking me to execute apply command, it will corrupt the previous \*state file isn’t it ?

I’m confused, why are you making an unsubstantiated claim that a standard `terraform apply` operation will “corrupt” anything?

Furthermore, quoting from the relevant official upgrade guide at [https://developer.hashicorp.com/terraform/language/v1.1.x/upgrade-guides/0-13](https://developer.hashicorp.com/terraform/language/v1.1.x/upgrade-guides/0-13):

> For this upgrade in particular, completing the upgrade will require running `terraform apply` with Terraform 0.13 after upgrading in order to apply some upgrades to the Terraform state, and we recommend doing that with no other changes pending.

> [@javed.alam1303](#):
>
> I do not wanna to mess the existing infrastructure.

So don’t “mess” with it. Verify the apply will not be changing anything of note before confirming it.