hashicorp / terraform-provider-awscc

Terraform AWS Cloud Control provider
https://registry.terraform.io/providers/hashicorp/awscc/latest/docs
Mozilla Public License 2.0
249 stars 114 forks source link

The terraform-provider-awscc_v0.52.0_x5 plugin crashed! #968

Open sameer2907 opened 1 year ago

sameer2907 commented 1 year ago

Community Note

Terraform CLI and Terraform AWS Cloud Control Provider Version

Affected Resource(s)

Terraform Configuration Files

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

resource "awscc_chatbot_slack_channel_configuration" "chatbot_slack_config_prod" {
  configuration_name = "api-gateway-5xx-alerts-prod"
  logging_level      = "INFO"
  iam_role_arn       = "arn:aws:iam::${data.aws_caller_identity.current.account_id}:role/AWS-Chatbot-Slack-Notifications-Role"
  slack_channel_id   = var.slack_prod_microservice_alerts_channel_id
  slack_workspace_id = var.slack_workspace_id
  sns_topic_arns     = [aws_sns_topic.api_gateway_5xx_topic_prod.arn]
}

Debug Output

Panic Output

Expected Behavior

Actual Behavior

awscc_chatbot_slack_channel_configuration.chatbot_slack_config_prod: Creating... ╷ │ Error: Plugin did not respond │ │ The plugin encountered an error, and failed to respond to the │ plugin6.(*GRPCProvider).ApplyResourceChange call. The plugin logs may │ contain more details. ╵

Stack trace from the terraform-provider-awscc_v0.52.0_x5 plugin:

panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xac17c1] Error: The terraform-provider-awscc_v0.52.0_x5 plugin crashed!

Steps to Reproduce

  1. terraform apply

Important Factoids

References

ewbankkit commented 1 year ago

@sameer2907 Thanks for raising this issue 👏. Do you have a stack trace that you could add to the issue?

mykobor commented 1 year ago

I got the same error in the GitHub Actions workflow. After debugging it was found, that problem happened because of missing permissions of deployment role. @sameer2907, try to add the following actions: