Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version v4.41.0 not published #3910

Closed
3 tasks done
nikolay opened this issue Sep 5, 2024 · 4 comments
Closed
3 tasks done

Version v4.41.0 not published #3910

nikolay opened this issue Sep 5, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@nikolay
Copy link

nikolay commented Sep 5, 2024

Confirmation

  • This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
  • I have searched the issue tracker and my issue isn't already found.
  • I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform v1.9.5
on darwin_arm64
+ provider registry.terraform.io/cloudflare/cloudflare v4.40.0

Terraform configuration files

provider "cloudflare" {
  api_token = var.cloudflare_api_token
}

terraform {
  required_version = "1.9.5"
  cloud {
    organization = "[REDACTED]"
    workspaces {
      name = "[REDACTED]"
    }
  }
  required_providers {
    cloudflare = {
      source  = "cloudflare/cloudflare"
      version = "4.41.0"
    }
  }
}

Expected output

$ terraform init -upgrade
Initializing HCP Terraform...

Actual output

$ terraform init -upgrade
Initializing HCP Terraform...
Initializing provider plugins...
- Finding cloudflare/cloudflare versions matching "4.41.0"...
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider cloudflare/cloudflare: no
│ available releases match the given constraints 4.41.0
╵

Steps to reproduce

  1. Bump provider version to 4.41.0 in versions.tf
  2. Upgrade the provider in the .terraform.lock.hcl with terraform init --upgrade

References

https://registry.terraform.io/providers/cloudflare/cloudflare/latest

@nikolay nikolay added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 5, 2024
Copy link
Contributor

github-actions bot commented Sep 5, 2024

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 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.

Copy link
Contributor

github-actions bot commented Sep 5, 2024

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

@github-actions github-actions bot added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 5, 2024
@wookets
Copy link

wookets commented Sep 5, 2024

I'm also experiencing this issue.

@jacobbednarz jacobbednarz closed this as not planned Won't fix, can't repro, duplicate, stale Sep 5, 2024
@jacobbednarz
Copy link
Member

hashicorp are aware (and have been for some time now) and still investigating the cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants