Error: string is required when create resource aws_default_vpc_dhcp_options

[rollcabbage]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.2.3
on darwin_amd64

Affected Resource(s)

• aws_default_vpc_dhcp_options

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

module "my_module" {
  source = "../../modules/platform/default_vpc"
}

module "default_vpc" {
  source = "trussworks/destroy-default-vpc/aws"
  region = "ap-northeast-1"
  azs    = ["a", "c", "d"]
}

Expected Behavior

terraform plan without error

Actual Behavior

Error: Failed to decode resource from state
Error decoding
"module.my_module.module.default_vpc.aws_default_vpc_dhcp_options.default"
from previous state: string is required
Error: string is required

Steps to Reproduce

1. terraform plan

Important Factoids

Occurred after using v4.20.1

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v4.20.1

issue #25562 also be experienced.

References

• r/aws_default_vpc_dhcp_options: Fix v4.20.0 regression with TypeList vs. TypeString #25562

[ewbankkit]

@rollcabbage Thanks for raising this issue 👏.
Do you know which version of the Terraform AWS Provider was used to create the aws_default_vpc_dhcp_options resource that reports the string is required error?
Do you have access to the Terraform state file? If so, could you paste the attributes for the resources (sanitized if necessary)?
Thanks.

[rollcabbage]

@ewbankkit Thanks for your replay.

which version of the Terraform AWS Provider was used

I used v4.20.1

Below is my tfstate.

{
      "module": "module. my_module.module.default_vpc",
      "mode": "managed",
      "type": "aws_default_vpc_dhcp_options",
      "name": "default",
      "provider": "provider[\"registry.terraform.io/hashicorp/aws\"]",
      "instances": [
        {
          "schema_version": 0,
          "attributes": {
            "arn": "arn:aws:ec2:ap-northeast-1:*********:dhcp-options/dopt-0789ca4a7049f9141",
            "domain_name": "ap-northeast-1.compute.internal",
            "domain_name_servers": [
              "AmazonProvidedDNS"
            ],
            "id": "dopt-0789ca4a7049f9141",
            "netbios_name_servers": [],
            "netbios_node_type": "",
            "ntp_servers": [],
            "owner_id": "***********",
            "tags": {
              "Automation": "terraform",
              "Name": "default"
            },
            "tags_all": {
              "Automation": "terraform",
              "Name": "default"
            }
          },
          "sensitive_attributes": [],
          "private": "bnVsbA==",
          "dependencies": [
            "module. my_module.module.default_vpc.aws_default_vpc.default"
          ]
        }
      ]
    },

[ewbankkit]

@rollcabbage Thanks for the response.
The error you experienced will be just for those aws_default_vpc_dhcp_options resources created with v4.20.0 of the Terraform Provider, before v4.20.1 was available.
Due to the short time window that this bug could have been caused in and the fact that deleting an aws_default_vpc_dhcp_options resource doesn't delete the underlying AWS DHCP Options Set, just removes the Terraform resource from state, please remove the affected resource (e.g. terraform destroy -target module.my_module.module.default_vpc.aws_default_vpc_dhcp_options.default) and then create it again with v4.20.1.

[rollcabbage]

@ewbankkit Thank you so much. I fixed this issue by your way.

[github-actions]

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.