[Bug]: aws_apigatewayv2_deployment not working for socket api

[diegogonzalezfe]

Terraform Core Version

1.7.4

AWS Provider Version

5.38.0

Affected Resource(s)

aws_apigatewayv2_deployment

Expected Behavior

On creation/redeployment, the resource is created correctly.

Actual Behavior

Stage deployment is not performed.

Relevant Error/Panic Output Snippet

Terraform log:

...
module.socket-api-order-gateway.aws_apigatewayv2_deployment.xxx: Creating...
module.socket-api-order-gateway.aws_apigatewayv2_deployment.xxx: Creation complete after 1s [id=of9zuj]

AWS Console (API Stage):

Active deployment
-

Terraform Configuration Files

resource "aws_apigatewayv2_api" "xxx" {
  name                       = "xxx"
  protocol_type              = "WEBSOCKET"
  route_selection_expression = "xxx"
}

resource "aws_apigatewayv2_stage" "xxx" {
  api_id = aws_apigatewayv2_api.xxx.id
  name   = xxx
}

resource "aws_apigatewayv2_deployment" "xxx" {
  api_id = xxx

  depends_on = [
    aws_apigatewayv2_route.xxx
  ]

  triggers = {
    redeployment = sha1(join(",", tolist([
      jsonencode(aws_apigatewayv2_route.xxx),
      jsonencode(aws_apigatewayv2_integration.xxx),
      jsonencode(aws_apigatewayv2_model.xxx),
      jsonencode(aws_apigatewayv2_route_response.xxx)
    ])))
  }
}

Steps to Reproduce

terraform init terraform apply

Debug Output

NA

Panic Output

NA

Important Factoids

Our issue is that in the creation of the deployment for the stage, the terraform execution seems correct but it has no effect, our API Gateway is a websocket.

References

No response

Would you like to implement a fix?

No

[github-actions[bot]]

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.

[justinretzolk]

Hey @diegogonzalezfe 👋 Thank you for taking the time to raise this! My initial thought it that given that there aren't any errors being thrown, this may be configuration related rather than a bug with the provider. Are you able to supply debug logs (redacted as needed)?

[bryantbiggs]

@diegogonzalezfe you need to add the deployment_id into your stage:

resource "aws_apigatewayv2_stage" "xxx" {
  api_id        = aws_apigatewayv2_api.xxx.id
+ deployment_id = aws_apigatewayv2_deployment.xxx.id
  name          = xxx
}

[justinretzolk]

@diegogonzalezfe 👋 Were you able to test the suggestion above to see if it resolves your issue?