hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.76k stars 9.11k forks source link

Apprunner connection with git #22496

Closed Ram2322 closed 4 days ago

Ram2322 commented 2 years ago

Hi Terraform team, We are able to provision aws app runner using terraform, but getting pending handshake in git connection. As per following note NOTE: After creation, you must complete the authentication handshake using the App Runner console. When we tried to completed handshake it is trying to connect git again. Please assist me.

justinretzolk commented 2 years ago

Hi @Ram2322 👋 Thank you for taking the time to file this issue. So that we have the necessary information in order to look into this, can you provide all of the information requested in the issue template?

michael-stevens commented 2 years ago

Hi, I'm also seeing this issue, here's my go at the template:

Terraform CLI Version & provider version:

Terraform v1.1.7
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v4.5.0
+ provider registry.terraform.io/hashicorp/random v3.1.0

Affected resources:

aws_apprunner_connection

Terraform config file:

resource "aws_apprunner_connection" "github" {
  connection_name = "github"
  provider_type   = "GITHUB"

}

Terraform debug output:

this is super long and probably contains private data?

Panic output:

n/a

Expected behaviour:

Connection created, able to complete it in aws console

Actual behaviour:

Unable to create in aws console, insists on creating new connection

Steps to reproduce:

terraform apply

Attempt to complete connection in console

Important factoids:

Seeing as this fails in the console step is it actually a terraform issue?

bryantbiggs commented 2 years ago

duplicate of #19825 - I am not seeing this same behavior - I have been able to create several GitHub connections without issue

github-actions[bot] commented 1 month ago

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!