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

[BUG] OpenTofu registry is missing GPG keys #1385

Open
egrosdou01 opened this issue Aug 9, 2024 · 1 comment
Open

[BUG] OpenTofu registry is missing GPG keys #1385

egrosdou01 opened this issue Aug 9, 2024 · 1 comment
Assignees
Labels

Comments

@egrosdou01
Copy link

Rancher Server Setup

  • Rancher version: 2.8.5
  • Installation option (Docker install/Helm Chart):
    • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): Helm chart installation on support platform.
  • Proxy/Cert Details:

Provider Information

  • What is the version of the Rancher v2 Terraform Provider in use? v4.1.0
  • What is the version of Terraform OpenTofu in use? OpenTofu v1.8.1 on darwin_arm64

Describe the bug

Basically, the GPG keys of this provider are missing in the OpenTofu module registry. When performing tofu init we can see the below message.

- Installing rancher/rancher2 v4.1.0...
- Installed rancher/rancher2 v4.1.0. Signature validation was skipped due to the registry not containing GPG keys for this provider

To Reproduce

  1. Install OpenTofu
  2. Execute tofu init

Actual Result

- Installing rancher/rancher2 v4.1.0...
- Installed rancher/rancher2 v4.1.0. Signature validation was skipped due to the registry not containing GPG keys for this provider

Expected Result

The rancher2 provider should be downloaded and verified.

@matttrach matttrach assigned matttrach and unassigned matttrach Aug 27, 2024
@matttrach matttrach self-assigned this Sep 5, 2024
@matttrach
Copy link
Collaborator

We don't specifically support open Tofu directly, we had an issue with GPG keys in the Terraform registry a while back which we resolved by extending the expiration date. It is possible that this was resolved at the same time, but we don't have any testing process in place to validate. @egrosdou01 has this been resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants