aws_iam_openid_connect_provider rejects valid "url"s

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.1.9
on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v4.27.0

Affected Resource(s)

• aws_iam_openid_connect_provider

Terraform Configuration Files

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

variable "my_bitbucket_org" {
  type        = string
  description = "the name of my bitbucket org"
  default     = "myorg"
}
provider "aws" {
  region = "us-east-1"
}
locals {
  oidc_url = "api.bitbucket.org/2.0/workspaces/${var.my_bitbucket_org}/pipelines-config/identity/oidc"
}
resource "aws_iam_openid_connect_provider" "bitbucket_pipelines_oidc" {
  url             = local.oidc_url
  thumbprint_list = [] # TODO
  client_id_list  = [] # TODO
}

Debug Output

plan debug logs

Expected Behavior

the provider should have accepted the protocol-less "url" that BitBucket provides. If I were to enter the same protocol-less url in the AWS IAM console, the OIDC-provider resource would be created successfully.

Actual Behavior

The resource marks my "url" as invalid, despite the fact that the "url" is a valid iss claim.

Steps to Reproduce

1. terraform plan