Errors when upgrading to terraform 0.13 about terraform-aws-notify-slack HOT 9 CLOSED

I had the same problem.
I started with a clean plan in Terraform 0.12.29 and module version 3.5 (and a clean git workspace)
I pinned the module version to 4.0.0, ran terraform_0.13.5 0.13upgrade and terraform_0.13 init. Both were clean.
I get the errors above upon running terraform_0.13.5 plan

So I stashed my changes, and using Terraform 0.12.29 did a terrafrom init && terraform state rm each of these three data objects. Then brought back my 0.13 changes, terraform_0.13.5 init, and was able to apply the changes between 3.5 and 4.0.

from terraform-aws-notify-slack.

Need use terraform replace, like this

terraform state replace-provider 'registry.terraform.io/-/local' 'registry.terraform.io/hashicorp/local'

for check your situation just do before terraform providers.

from terraform-aws-notify-slack.

Possibly, this has to do with your change of the lambda submodule, which removed resources that were still in use? From the terraform 0.13 upgrade guide linked above

If you remove a resource block (or a module block for a module that contains resource blocks) before the first terraform apply, you may see a message like this reflecting that Terraform cannot determine which provider configuration the existing object ought to be managed by:

Error: Provider configuration not present

To work with null_resource.foo its original provider configuration at
provider["registry.terraform.io/-/aws"] is required, but it has been removed.
This occurs when a provider configuration is removed while objects created by
that provider still exist in the state. Re-add the provider configuration to
destroy aws_instance.example, after which you can remove the provider
configuration again.

In this specific upgrade situation the problem is actually the missing resource block rather than the missing provider block: Terraform would normally refer to the configuration to see if this resource has an explicit provider argument that would override the default strategy for selecting a provider. If you see the above after upgrading, re-add the resource mentioned in the error message until you've completed the upgrade.

So, I think you need to add back the missing resources that were deleted?

from terraform-aws-notify-slack.

Since these were just 'data' objects, not 'resources', I deleted them from the remote state using terraform state rm, and it seems to have unstuck me. Still, there should probably be something in the README.md about how to make the transition from the 3.x to 4.x versions of this module.

from terraform-aws-notify-slack.

which version of 0.13.x are you using? there were known state migration issues on the earlier versions of 0.13 (0.13.1-0.13.2). its not an issue with the module here, but more with terraform itself

• https://github.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md#0132-september-02-2020
• https://github.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md#0132-september-02-2020

from terraform-aws-notify-slack.

using terraform 0.13.4

from terraform-aws-notify-slack.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-notify-slack.

This issue was automatically closed because of stale in 10 days

from terraform-aws-notify-slack.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from terraform-aws-notify-slack.