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

New releases required because of "openpgp: signature made by unknown entity." error #152

Open
sdurrheimer opened this issue May 4, 2021 · 3 comments

Comments

@sdurrheimer
Copy link

Terraform changed their PGP HC Public key which makes provider download failing on older terraform versions.

Could you release new docker images for the following versions containing the new key:

  • 0.11.15
  • 0.12.31
  • 0.13.7
  • 0.14.11

The error encountered:

Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...

Error installing provider "aws": openpgp: signature made by unknown entity.

Terraform analyses the configuration and state and automatically downloads
plugins for the providers used. However, when attempting to download this
plugin an unexpected error occured.

This may be caused if for some reason Terraform is unable to reach the
plugin repository. The repository may be unreachable if access is blocked
by a firewall.
@ljfranklin
Copy link
Owner

Unfortunately I don't have the CI plumping in place to release hotfixes to old versions. I don't think a need has come up before since Terraform hasn't reached 1.0 yet so there haven't been any LTS concerns.

I'm leaning towards not updating the old releases as a nudge towards getting folks to update to latest. If you absolutely need to stay on an old version, you can build your own Docker image starting with FROM ljfranklin/terraform-resource:0.14.10 and replace the /usr/local/bin/terraform executable with the 0.14.11 version.

@sdurrheimer
Copy link
Author

We have able to build new images ourselves for now using your build-image script in order to unblock our customers.
We opened this issue have we thought probably other users might benefit from having those new versions available on the upstream repository.

Upgrading to 0.15.1 would have been a valid technical solution, yes, but not everyone has that time and time is money with customers.

So we will keep our images until those projects can be upgraded, I guess 🙂

@dlresende
Copy link

We hit this issue as well.

We might end up doing what @sdurrheimer did, or something else.

Thought I'd share as another data point.

Also sharing this blog post from Hashicorp with more details about the issue.

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

No branches or pull requests

3 participants