-
Notifications
You must be signed in to change notification settings - Fork 60
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
[FEATURE] Submit GPG public key to the OpenTofu registry #221
Comments
[Triage] |
Hey @tthompson-figma after reading some license and OpenTofu documentation I dont see a problem in creating Submit new Provider Signing Key request, this will also improve the OpenSearch provider footprint in OpenTofu community. So after adding the key should I be able to find the OpenSearch in https://opentofu.org/registry/ ? Also does it take care of backfilling all the previous releases https://github.com/opensearch-project/terraform-provider-opensearch/releases ? Thank you |
That's right! Note that you might not see the provider in https://search.opentofu.org/ but it'll still be present in the registry API! |
Thanks @tthompson-figma so the OpenSearch terraform provider will be present on https://search.opentofu.org/ once the Submit new Provider Signing Key request is completed? |
The provider is already present in the registry, just without its GPG key submitted. You can see the existing metadata for the provider here: curl 'https://registry.terraform.io/v1/providers/opensearch-project/opensearch' | jq Provider downloads will include the GPG key and signatures once you've submitted the key to the registry! |
Yes its present in Hashicorp terraform registry https://registry.terraform.io/providers/opensearch-project/opensearch/latest, not in OpenTofu registry, was checking it will be part of https://search.opentofu.org/ or https://opentofu.org/registry/ once the requests is submitted ? |
Agh sorry, I used the wrong registry in the |
I have merged the key into the OpenTofu Registry and it should be online shortly. I believe this issue can be closed as resolved. Thank you to everyone involved here for helping make OpenTofu more secure! |
Thanks all for the help!! 🙇 |
We would like to migrate to OpenTofu with all providers' GPG signatures validated. However, OpenTofu skips validation for this provider because the OpenTofu registry does not have this provider's GPG key.
You can follow this link to submit it: Submit new Provider Signing Key
If you don't have access to the public key anymore, you can retrieve it from the Terraform registry:
Note: For security reasons, it has to be submitted by the provider author for the OpenTofu registry to accept it.
Alternatives considered
Out-of-band GPG validation for providers missing keys in the OpenTofu registry. This is a pain :)
Additional context
OpenTofu is a fork of Terraform that is open-source, community-driven, and managed by the Linux Foundation.
Hashicorp opentofu/roadmap#24 (comment) for the terraform provider registry to disallow usage with things other than terraform, so OpenTofu had to build its own registry.
Potential impact
Allows OpenTofu users to use this provider with the same security guarantees they would using Terraform.
The text was updated successfully, but these errors were encountered: