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
Submit signatures for provider to OpenTofu registry #344
Comments
@kevcube just ran into this myself and came here to open this issue -- Good to see you ahead of me 🙌 |
@aknysh since you're the lead contributor on this repo, pinging you to ask: Is this on your folks radar yet? We're running into the same with the template provider fork as well. |
Signing keys for any given provider can be uploaded by selecting "Submit new Provider Signing Key" from opentofu/registry's Issues page. Here's a recent example of one such submission. |
Adding to what @RDhar said, to submit a GPG key for a provider in a GitHub org, you need to be an org member and make your org membership public so the registry process can verify it. This method was chosen to avoid asking people for access to their GitHub account for verification. |
@Gowiem @kevcube the https://github.com/opentofu/registry/blob/main/keys/c/cloudposse/provider.asc |
Describe the Feature
output when using with opentofu:
Expected Behavior
Signatures in registry would be nice to have
Use Case
blank
Describe Ideal Solution
blank
Alternatives Considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: