[Bug]: aws_apigatewayv2_api domain name: Provider produced inconsistent final plan

[krzysztofdrys]

Terraform Core Version

v1.3.4

AWS Provider Version

v4.56.0

Affected Resource(s)

aws_apigatewayv2_domain_name

Expected Behavior

Domain name should be created

Actual Behavior

Domain name is not created

Relevant Error/Panic Output Snippet

╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for aws_apigatewayv2_domain_name.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .domain_name: was
│ cty.StringVal("[REDACTED URL]"), but now cty.StringVal("Example Pet Store").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵

Terraform Configuration Files

terraform {
  required_providers {
    aws = {
      source = "hashicorp/aws"
      version = "4.56.0"
    }
  }
}

variable "name" {}

variable "certificate_arn" {}

provider "aws" {
  region = "eu-west-1"
}

data "local_file" "openapi" {
  filename = "${path.module}/openapi.yaml"
}

# Stage and deployment
resource "aws_apigatewayv2_api" "this" {
  name          = var.name
  protocol_type = "HTTP"
  body          = data.local_file.openapi.content

  fail_on_warnings = true
}

resource "aws_apigatewayv2_domain_name" "this" {
  domain_name = aws_apigatewayv2_api.this.name

  domain_name_configuration {
    certificate_arn = var.certificate_arn
    endpoint_type   = "REGIONAL"
    security_policy = "TLS_1_2"
  }
}

local_file is OpenAPI 3.0 definition take from here https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-open-api.html

Steps to Reproduce

export TF_VAR_name="[REDACTED URL]"
export TF_VAR_certificate_arn="[valid arn]"

rm -rf .terraform
rm .terraform.lock.hcl
terraform init -input=false
terraform plan --out tfplan
terraform apply tfplan

Debug Output

tf_plan.log: https://gist.github.com/krzysztofdrys/93d57e83ac25f874eaaf8a8ae79df7a1
tf_apply.log: https://gist.github.com/krzysztofdrys/ed543eae5d25bc5b874d59faf1dd8e89

Panic Output

No response

Important Factoids

If you change provider version 4.46.0, terraform apply succeeds without any problems.

References

No response

Would you like to implement a fix?

Yes

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[Woody1193]

Is there any update on this? Have encountered same with provider version 5.22 and 5.52. Have also attempted to remedy by replacing triggers with depends_on.